| Commit message (Collapse) | Author | Age | Files | Lines |
| | |
|
| |\
| |
| | |
REL: Prepare for the NumPy 1.20.2 release.
|
| |/
|
|
|
| |
- Create the 1.20.2-changelog
- Update the 1.20.2-notes
|
| |\
| |
| | |
BUG: Fix small issues found with pytest-leaks
|
| |/
|
|
|
|
|
|
|
|
|
| |
None of these are particularly worrying as they either usually only
leak reference (and not memory) or appear in rare or almost impossible
error-paths, or are limited to the tests.
Unfortunately, this PR will not apply to 1.20.x, due to small changes
in the overrides.
Backport of gh-18670 (with two small differences)
|
| |\
| |
| | |
BUG: Fix small valgrind-found issues (#18651)
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* BUG: Fix small valgrind-found issues
This should be backportable. There was at least one that I could
not reproduce when running the tests again. And the new random-shuffle
tests give false-positives (which is just slightly annoying, considering
that we are very close to almost only "longdouble" related
false-positives)
* BUG: Add missing decref in user-dtype fallback paths
The missing decref here only leaks references and can never leak
actual memory fortunately.
* MAINT,TST: Simplify the "refcount logic" in the dispatch tests again
Using SETREF can be nice, but was just overcomplicating thing here...
|
| |\ \
| | |
| | | |
BUG: Fix ma coercion list-of-ma-arrays if they do not cast to bool
|
| | | | |
|
| | | | |
|
| | |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
There was a regression here due to force casting to bool, but if that
happens to fail (it does, but should not for strings). The mask
would just be dropped.
Of course masked arrays are held together by faith here, but its
a regression.
Closes gh-18551
|
| |\ \
| |/
|/| |
MAINT: Ensure that re-exported sub-modules are properly annotated
|
| | |
| |
| |
| | |
Aforementioned module was accidently marked as public
|
| | |
| |
| |
| |
| |
| |
| | |
Ensures that type checkers will allow the likes of:
>>> import numpy as np
>>> out = np.lib.stride_tricks.sliding_window_view(...)
|
| |/
|
|
|
|
|
|
|
| |
With `as_strided`, and the newly introduced `sliding_window_view` function, there are currently 2 public objects that can:
a. Only be imported from a private module
b. Are publicly documented to-be imported from aforementioned module
Both observations are problematic and in need of rectification.
This commit therefore moves `np.lib.stride_tricks` to the `PUBLIC_MODULES` list.
|
| |\
| |
| | |
CI: Update apt package list before Python install
|
| |/
|
|
| |
Closes #18613.
|
| |\
| |
| | |
BUG: NameError in numpy.distutils.fcompiler.compaq
|
| | |
| |
| | |
Fix a simple mistake in commit da0497fdf35 which can produce a NameError when installing numpy in MinGW/MSYS2.
|
| |\ \
| | |
| | | |
BUG: Fixed ``where`` keyword for ``np.mean`` & ``np.var`` methods
|
| | |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* Fixed keyword bug
* Added test case
* Reverted to original notation
* Added tests for var and std
Closes gh-18552
|
| | | |
|
| |\ \
| | |
| | | |
BUG: incorrect error fallthrough in nditer
|
| | |/
| |
| |
| | |
Fixup to gh-18450
|
| |\ \
| |/
|/| |
CI: Backport CI fixes from main.
|
| | |
| |
| |
| |
| |
| | |
NumPy does not build using the `--coverage` flag on Ubuntu 20.04, the
problem seems to be gcc 9.3.0-17. Work around that by running on Ubuntu
18.04 instead.
|
| |/
|
|
|
|
|
|
| |
The azure-pipeline test Linux_Python_38_32bit_full_with_asserts has
been failing after the release of the latest manylinux2010. Pin
the docker image to an earlier version to fix this.
Closes #18553.
|
| |\
| |
| | |
BUG: check if PyArray_malloc succeeded
|
| | | |
|
| | | |
|
| |\ \
| | |
| | | |
BUG: verify pointer against NULL before using it
|
| | |/ |
|
| |\ \
| | |
| | | |
BUG: remove nonsensical comparison of pointer < 0
|
| | |/ |
|
| |\ \
| |/
|/| |
BUG: Remove suspicious type casting
|
| | | |
|
| |/ |
|
| |\
| |
| | |
BUG: Segfault in nditer buffer dealloc for Object arrays
|
| |/ |
|
| |\
| |
| | |
BUG: Remove temporary change of descr/flags in VOID functions
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This is done using a hack around stack allocated arrays, which
requires some dark magic with respect to the setting the base
object (we skip normal arrays and INCREF/DECREF during base setting,
which _does_ work for such static arrays, but only if we give them
a (not quite) fake refcount of 1 and set the base and their type
correctly to PyArrayType.
Closes gh-15387
|
| |\ \
| | |
| | | |
BUG: Fix tiny memory leaks when ``like=`` overrides are used
|
| | |/
| |
| |
| |
| |
| |
| | |
I thought I had fixed these leaks, but it appears I missed some.
We probably should backport this to 1.20.x (its simple), but the leaks
are also pretty harmless unless someone uses `like=` hundrets of
thousands of times in a running program (and its a new fetaure).
|
| |\ \
| | |
| | | |
BUG: Fix refcount leak in f2py ``complex_double_from_pyobj``.
|
| | |/ |
|
| |\ \
| |/
|/| |
BUG: ``diagflat`` could overflow on windows or 32-bit platforms
|
| |/
|
|
| |
platforms
|
| |\
| |
| | |
MAINT: Update f2py from master.
|
| |/
|
|
|
| |
This will make it easier to backport the f2py fixes currently going
into master.
|