| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
| |
Also adds a minor code change
|
| |
|
| |
|
|
|
| |
Fixes #13598
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Increment stacklevel for warnings to account for NEP-18 overrides
For NumPy functions that make use of `__array_function__`, the appropriate the
stack level for warnings should generally be increased by 1 to account for
the override function defined in numpy.core.overrides.
Fixes GH-13329
* Update numpy/lib/type_check.py
Co-Authored-By: Sebastian Berg <sebastian@sipsolutions.net>
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
- Always enable __array_function__ overrides.
- Remove special cases for Python 2 compatibility.
- Document these changes in 1.17.0-notes.rst.
It will be good to see ASV numbers to understand the performance implications
of these changes. If need be, we can speed up NumPy functions internally by
using non-dispatched functions (with ``.__wrapped__``).
|
|
|
|
|
|
|
|
| |
* ported the refguide_check module from SciPy for usage
in NumPy docstring execution/ verification; added the
refguide_check run to Azure Mac OS CI
* adjusted NumPy docstrings such that refguide_check passes
|
| |
|
|
|
|
|
|
| |
Fixes gh-12263
We can't support generators with dispatch for ``__array_function__``.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* ENH: __array_function__ support for np.lib, part 2
xref GH12028
np.lib.npyio through np.lib.ufunclike
* Fix failures in numpy/core/tests/test_overrides.py
* CLN: handle depreaction in dispatchers for np.lib.ufunclike
* CLN: fewer dispatchers in lib.twodim_base
* CLN: fewer dispatchers in lib.shape_base
* CLN: more dispatcher consolidation
* BUG: fix test failure
* Use all method instead of function in assert_equal
* DOC: indicate n is array_like in scimath.logn
* MAINT: updates per review
* MAINT: more conservative changes in assert_array_equal
* MAINT: add back in comment
* MAINT: casting tweaks in assert_array_equal
* MAINT: fixes and tests for assert_array_equal on subclasses
|
|
|
|
|
|
|
|
|
|
|
|
| |
(#11813)
Fixes #11809.
* BUG: fix array_split incorrect behavior with array size bigger MAX_INT32
* TST: added test for array_split with array size greater MAX_INT32
* addressed review comments
|
|
|
|
| |
This allows np.ma.expand_dims to be removed
|
|
|
|
| |
This is the reduced version that does not allow any insertion of extra dimensions
|
| |
|
|\
| |
| | |
DOC: describe the expansion of take and apply_along_axis in detail
|
| |
| |
| |
| |
| |
| | |
Extracted from gh-8714
[ci-skip]
|
|/
|
|
| |
[ci skip]
|
|
|
| |
Before this addition, people could expect that only the last sub-array would have a different size. The added documentation and example make clear what the function really does.
|
| |
|
|
|
|
| |
[skip ci]
|
|
|
|
|
|
|
|
|
|
|
| |
Expand_dims works as documented when the index of the inserted NewAxis
in the resulting array satisfies -a.ndim - 1 <= index <= a.ndim.
However, when index > a.ndim index is replaced by a.ndim and, when
index < -a.ndim - 1, it is replaced by index + a.ndim + 1, which may be
negative and results in incorrect placement. The latter two cases are
now deprecated.
Closes #9100.
|
|
|
|
| |
[ci skip]
|
| |
|
|\
| |
| | |
BUG: Fix double-wrapping of object scalars
|
| |
| |
| |
| | |
Fixes #8642
|
|\ \
| | |
| | | |
DOC: Mention that expand_dims and squeeze are inverses
|
| | |
| | |
| | |
| | | |
[ci skip]
|
|/ /
| |
| | |
This adds to the documentation on `dstack` the notes from `hstack` and `vstack` about dimensionality requirements.
|
| | |
|
|/
|
|
|
|
|
| |
As a result, some exceptions change from ValueError to IndexError
This also changes the exception types raised in places where
normalize_axis_index is not quite appropriate
|
|
|
|
| |
Fixes #7454
|
|
|
|
| |
Copied from the implementation in core.shape_base.stack
|
|
|
|
|
|
|
| |
.transpose does not specify that it must return a view, so subclasses
(like np.ma.array) could otherwise break this.
This exposes some more need for matrix special casing.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Also:
ENH: Support arbitrary dimensionality of return value
MAINT: remove special casing
|
|
|
|
|
|
|
|
|
|
|
|
| |
* BUG: Closes issue #8419
Fixes issue in apply_along_axis() where func1d() returns a non ndarray
* BUG: Fix apply_along_axis() when func1d() returns a non-ndarray
Closes issue #8419. Fixes issue in apply_along_axis() where
func1d() returns a non ndarray by calling asanyarray() on
result. This commit fixes a too long line in the test case.
|
|
|
|
|
|
|
| |
This commit modifies the numpy.apply_along_axis() function so that if
it is called with an ndarray subclass, the internal func1d calls
receive subclass instances and the overall function returns an instance
of the subclass. There are two new tests for these two behaviours.
|
|
|
|
|
| |
The missing whitespace lead to inconsistent rendering in the
online documentation. [ci skip]
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Previously an empty array resulting from split always had dimension 1-D.
In Numpy 1.9 a FutureWarning was raised to notify users that it was
planned to preserve the dimensions of empty arrays in a future numpy
release. This removes the FutureWarning and implements preservation of
dimensions.
Note that there was a bug in numpy 1.9 and the dimensions of empty
arrays was already preserved in some cases and no warning was issued.
This PR fixes that inconsistency by preserving the dimensions in all
cases rather than fixing the bug, as the dimension preserving behavior
was already depended on by some users. See the discussion in gh-6575
about this change.
|
|\
| |
| | |
BUG: Make sure warning for array split is always applied
|
| |
| |
| |
| |
| |
| |
| |
| | |
Zero arrays can also occur with any of the partitions sub_arys[i]
induced by array_split, not just the final partition sub_arys[-1].
Modified by seberg.
Closes gh-5771
|