| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| | |
ENH: Allow ``where`` argument to override ``__array_ufunc__``
|
| |
| |
| |
| | |
override `__array_ufunc__`.
|
|/
|
|
|
|
|
|
| |
As discussed in
https://mail.python.org/archives/list/numpy-discussion@python.org/thread/UKZJACAP5FUG7KP2AQDPE4P5ADNWLOHZ/
This flag was always meant to be temporary, and cleaning it up is
long overdue.
|
|\
| |
| | |
DOC: Added explanation document on interoperability
|
| | |
|
|/
|
|
| |
Add conftest.py and pytest.ini files in doc directory
|
| |
|
|
|
|
|
|
|
|
| |
This:
* Fixes some broken references
* Cleans up some use of Python 2 aliases:
* Switches references to `np.string_` to describe `np.bytes_` instead
* Switches references to `np.unicode_` to describe `np.str_` instead
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* 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
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Fix missing np prefix.
Fix missing definitions.
Use print function instead of the statement.
Add seed to make output repeatable.
|
| |
|
| |
|
|\
| |
| | |
DOC: Resolve bad references in Sphinx warnings
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
|/ |
|
|
|
|
|
|
|
|
| |
In some cases the documentation examples failed with an
AttributeError because the next method was not there. In a
few other cases it still worked but may be more future-proof
and ideomatic if they used the next function instead of the
next method.
|
|
|
|
|
| |
Other libraries are relying on this now, and the protocol has been stable
since 1.13.0
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
This mixin class provides an easy way to implement arithmetic operators
that defer to __array_ufunc__ like numpy.ndarray in non-ndarray
subclasses.
|
| |
|
| |
|
|
|
|
| |
The text had been changed following the suggestion of @njsmith, but
somehow I had forgotten to delete the original.
|
| |
|
|
|
|
|
| |
This includes the use of super everywhere, and in the brief
description of __array_ufunc__ in the reference section.
|
| |
|
| |
|
|
|
|
|
|
| |
Previously when __array_ufunc__ for one of the ufunc arguments was
called, that arguments position was passed in the call. This PR removes
that argument as proposed in gh-5986.
|
|
|
|
|
|
|
|
| |
The first commit in changing __numpy_ufunc__ by removing the index
argument and making the out argument value always a tuple. These changes
were proposed in gh-5986 and have been accepted. Renaming before further
changes avoids triggering tests in scipy and astropy while keeping the
numpy tests working.
|
|
|
|
|
|
|
|
|
| |
Instances remain for NumpyVersion and Numpy.rec.fromarrays that are
references to code.
Release notes were left unchanged.
see issue #7986
|
|
|
|
|
|
| |
* Change ".. function::" -> ".. method::"
* Remove "self" argument
* Change "self" to "obj" in __array_finalize__
|
| |
|
|
|
|
| |
Also correct its documented default value.
|
|
|
|
|
|
|
|
|
|
|
| |
This update adds a section better describing record arrays in the user
guide (numpy/doc/structured_arrays.py).
It also corrects nomenclature, such that "structured array" refers to
ndarrays with structured dtype, "record array" refers to modified
ndarrays as created by np.rec.array, and "recarray" refers to ndarrays
viewed as np.recarray. See the note at the end of the structured
array user guide.
|
|
|
|
|
|
|
|
|
| |
Installation docs still stated Python 2.4 is supported, while not mentioning
3.x at all. Also corrected the statement that distutils is in python-dev on
Debian, while it's actually in the main package.
Several parts of the dev docs and some comments also referenced now-irrelevant
2.5 bugs/limitations.
|
|
|
|
| |
Make it 1.10.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add a special case to the implementation of ndarray.__mul__ et al. that
refuses to work on other objects that are not ndarray subclasses and
implement both __numpy_ufunc__ and __r*__.
This way, execution passes first to the custom __r*__ method, which
makes it possible to have e.g. __mul__ and np.multiply do different
things.
Additionally, disable one __array_priority__ special case handling when
also __numpy_ufunc__ is defined.
|
|
|
|
|
| |
Cross-reference it from Ufunc documentation and mention the version it
was added.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In python3 range is an iterator and `xrange` has been removed. This has
two consequence for code:
1) Where a list is needed `list(range(...))` must be used.
2) `xrange` must be replaced by `range`
Both of these changes also work in python2 and this patch makes both.
There are three places fixed that do not need it, but I left them in
so that the result would be `xrange` clean.
Closes #3092
|
| |
|
| |
|
| |
|
|
|
|
| |
1240, 1241. docstrings, full unit-test coverage, C-based vectorized string operations.
|