| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
|
| |
* Created fundamentals doc for explanations in ufunc reference doc
* Move explanatory material on ufuncs and broadcasting from the
reference guide to the ufunc fundamentals and/or broadcasting
document in the user guide
* Added examples for ufunc method arguments
* Reorganized broadcasting duplicate content from ufuncs doc
Co-authored-by: Melissa Weber Mendonça <melissawm@gmail.com>
|
|\
| |
| | |
MAINT: Implement new style promotion for `np.result_type`, etc.
|
| | |
|
| | |
|
| |
| |
| | |
Co-authored-by: Ross Barnowski <rossbar@berkeley.edu>
|
| | |
|
|/
|
|
|
|
|
|
|
|
|
|
| |
Also, for now enforce *all* outputs. That is more conservative, and
obviously won't work for certain functions in scipy that have multiple
outputs of different types, but it seems a bit safer to me right now.
Maybe at some point we have an idea of how to "modify" what the `dtype`
means. I am not sure how! By allowing the ufunc itself to interpret
how to translte it to a `signature`? By giving it a distinct meaning?
Yes, this might narrow us down a bit... but...
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
Adds the ufunc class to the documentation so that it is included
in the generated html docs and all links to it work.
Slightly modify ufunc docstring to remove unrecognized heading
name.
|
|
|
|
|
|
|
| |
Describing ufunc copy behaviour when input and output overlaps.
Closes #16749
Co-authored-by: Ross Barnowski <rossbar@berkeley.edu>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* DOC: Fixes for 18 broken links
This, with PR #16465, should fix nearly all the remaining broken links
on the site. 4 or 5 others should be easy to fix and just
need attention from someone more knowledgeable -- will
open an issue. For release notes with dead links,
I could usually find links on archive.org for roughly contemporary
versions.
* DOC: Update to "Fixes for 18 broken links #16472"
* Obsolete links, previously commented out, now deleted:
https://github.com/numpy/numpy/pull/16472#discussion_r433928958
* Semantic markup for reference to Python class:
https://github.com/numpy/numpy/pull/16472#discussion_r433553928
* Missing :ref: in internal link:
https://github.com/numpy/numpy/pull/16472#discussion_r433554484
Not included: Resolution on using external/internal doc link in .py:
https://github.com/numpy/numpy/pull/16472#discussion_r433554824
* DOC: Add internal link for 'Fixes for 18 broken links' PR #16472
Making reference [1] an internal link in function_base.py => numpy.vectorize.html
* DOC: Redirect 2 link fixes in PR #16472
* governance.rst link reverted
* ununcs.rst `overridden` link goes where it was meant to
per https://github.com/numpy/numpy/pull/16472#pullrequestreview-424666070
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
According to the docs, the list can be of lengths 1, 2, or 3, but only
length 3 appears to work:
```
>>> import numpy as np
>>> np.sin(1, extobj=[16, 1, lambda: None])
0.8414709848078965
>>> np.sin(1, extobj=[16, 1])
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
TypeError: UFUNC_PYVALS must be a length 3 list.
>>> np.sin(1, extobj=[16])
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
TypeError: UFUNC_PYVALS must be a length 3 list.
```
|
|
|
|
| |
See #15214
|
|\
| |
| | |
API: Forbid Q<->m safe casting
|
| |
| |
| |
| |
| |
| |
| |
| | |
That is, uint64 <-> timedelta64.
Allowing this casting was weird, because Q<->q is forbidden, yet q and m are both int64.
This fixes gh-12927
|
| | |
|
|/ |
|
|
|
|
|
|
| |
The Unicode checkmark doesn't necessarily have the same width as the
ASCII characters, even when rendered with a fixed-width font, so the
casting table can be misaligned when the checkmark is used.
|
| |
|
|
|
| |
Changed default value of `__array_priority__` to correct value.
|
| |
|
| |
|
| |
|
|
|
|
| |
Both in the general documentation and in the release notes.
|
| |
|
|
|
|
|
|
| |
Both in the general documentation and in the release notes.
For the latter, also include a description of ``axes``,
which was missing so far.
|
|
|
|
|
|
|
|
|
|
|
|
| |
* DOC: mention we can return unitinitialized values
* squash and rebase, extend explanation and improve docstring template
* MAINT: Spelling fixes for docstrings.
[ci skip]
* MAINT: Update following feedback.
|
| |
|
|
|
|
| |
Fixes #8772
|
|
|
|
|
|
| |
The `ufunc.signature` attribute is the generalized ufunc signature, while the
optional `signature` parameter in `ufunc.__call__` refers to the loop type.
[ci skip].
|
|
|
| |
[ci skip]
|
|
|
|
|
| |
Also ensure that __array_ufunc__ is referenced in the output type
determination.
|
| |
|
|
|
|
|
|
|
| |
* DOC: Update ufuncs.rst to mention the option of an axis tuple
fixes issue gh-9131.
ufuncs.rst now mentions that the axis may be assigned a tuple of int for reduce.
Also fixed broken "{op}.reduce" link on the webpage in the same article.
|
| |
|
|\
| |
| | |
ENH: Show full PEP 457 argument lists for ufuncs
|
| | |
|
|/ |
|
| |
|
|
|
|
| |
xref GH8932
|
| |
|
| |
|
|\
| |
| | |
DOC: added a whitespace so that sphinx directive displays correctly
|
| | |
|
|/ |
|
|
|
|
|
|
|
|
|
| |
Instances remain for NumpyVersion and Numpy.rec.fromarrays that are
references to code.
Release notes were left unchanged.
see issue #7986
|
|
|
|
| |
[skip ci]
|