| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |\
| |
| | |
MRG, ENH: added edge keyword argument to digitize
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| |/
|
|
|
|
| |
ENH: added edge keyword argument to digitize
added test
|
| |\
| |
| | |
REL: Update master after 1.19.1 release.
|
| |/ |
|
| |\
| |
| | |
DOC: Add ufunc docstring to generated docs.
|
| | |
| |
| |
| |
| |
| |
| |
| | |
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.
|
| |\ \
| | |
| | | |
DEP: Deprecate NumPy object scalars
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
NumPy object scalars should not exist, since they should always
just return the actual scalar in the first place. Put a deprecation
warning in place to be rapidly changed into a TypeError.
Once allocating it gives an error, we can make all methods raise
errors (with the exception of `__new__`.
|
| | | |
| | |
| | |
| | |
| | |
| | | |
Add new attribute `dispatch` to umath generator,
same usage as the current attribute `simd` but requires
the name of the dispatch-able source without its extension
rather than CPU features names.
|
| | |/
|/|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
BadZipFile (#15604)
Previously if you gave an invalid zip file to NpzFile, zipfile_factory would raise BadZipFile and NpzFile.__exit__ would be called, which accessed members which had not yet been set, leading to a confusing second exception like this:
zipfile.BadZipFile: File is not a zip file
Exception ignored in: <function NpzFile.__del__ at 0x9b8ef0>
Traceback (most recent call last):
File "numpy/lib/npyio.py", line 230, in __del__
self.close()
File "numpy/lib/npyio.py", line 221, in close
if self.zip is not None:
AttributeError: 'NpzFile' object has no attribute 'zip'
This change makes __exit__ safe even when __init__ did not complete.
|
| |\ \
| | |
| | | |
BUG: Fix string/bytes to complex assignment
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This was a regression, which happened because of discrepencies
between setting a single item from a string (which was not possible)
and casting from a string to array (which was possible before).
The seconnd code path changed, relying on the former behaviour, which
broke it. This fixes the issue by bringing the second branch in line.
Closes gh-16909
|
| |\ \ \
| | | |
| | | | |
MAINT: Bump hypothesis from 5.19.1 to 5.20.2
|
| |/ / /
| | |
| | |
| | |
| | |
| | |
| | | |
Bumps [hypothesis](https://github.com/HypothesisWorks/hypothesis) from 5.19.1 to 5.20.2.
- [Release notes](https://github.com/HypothesisWorks/hypothesis/releases)
- [Commits](https://github.com/HypothesisWorks/hypothesis/compare/hypothesis-python-5.19.1...hypothesis-python-5.20.2)
Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
|
| |\ \ \
| | | |
| | | | |
MNT: also use Py_SET_REFCNT instead of Py_REFCNT
|
| | | | |
| | | |
| | | |
| | | | |
This is required to support Python 3.10.
|
| | |/ /
|/| |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Since #15893, test_large_zip's actual test is run in a child process,
so when this test raises a MemoryError exception, the exception is
lost and the @requires_memory decorator can't catch it to return
an xfail.
This commit uses a boolean variable in shared memory to flag if
the exception was raised, and in that case, re-raise it in the
parent process.
Fixes #16889
|
| | | |
| | |
| | |
| | |
| | | |
* MAINT: Remove Duplicated Code (function extract rmap)
Co-authored-by: Ross Barnowski <rossbar@berkeley.edu>
|
| |\ \ \
| | | |
| | | | |
BUG: Remove non-threadsafe sigint handling from fft calculation
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The fft calculation is the only point in our code where this function
is used. Allowing Ctrl+C, in FFT specifically used have more reasons,
since before pocketfft, some array-sizes could lead to very large
run-times.
Pocketfft fixed that issue, and now FFT is not really any slower,
faster, or memory hungry than any other NumPy operation so it feels
it does not need this handling. Rather, if we can find a better
solution, it should also be added to more functions.
The reason for removal is that it is not only unsafe while the
FFT is running (in theory). Multiple, threaded FFT run can easily
leave the signal handler in a bad state, causing crashes if Ctrl+C
(sigint) is given at any point after the call.
It would be possible to patch that over, by only resetting the
signal handler if we actually changed it (or even more complex
tricks), or possibly only using this technique when on the main
thread.
But, all of these solutions seem to complicate things, when the
main reason for why allowing sigint seems useful is gone with
pocketfft.
|
| |\ \ \ \
| | | | |
| | | | | |
DEP: Deprecate ufunc.outer with matrix inputs
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Previously we converted matrices to arrays for the user, since
`np.outer` does not make sense for matrix. This deprecates that
usage (which in almost all cases will result in an error).
The main reason for this deprecation is to remove all direct
references of matrix from the NumPy codebase, so that it is
easier to move it out of NumPy eventually.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This simplifies the reshaping logic to use the NewShape function
(this was previously impossible due to the split of umath and
multiarray).
It adds new errors if reshapes are bad, which currently is only
possible for bad subclasses. However, `np.matrix` is the main bad
subclass here, so this is in preparation of deprecating it.
|
| |\ \ \ \ \
| | | | | |
| | | | | | |
BUG,DOC: Fix bad MPL kwarg in docs
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Invalide kwarg to imshow causes failures in the plot directive
for docs builds using MPL > v3.3
|
| |/ / / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Describing ufunc copy behaviour when input and output overlaps.
Closes #16749
Co-authored-by: Ross Barnowski <rossbar@berkeley.edu>
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
leeyspaul/clarify-new-feature-requirements-in-contributing-docs
DOC: clarify whats required for new features see #13924
|
| | | | | | | |
|
| | | | | | |
| | | | | |
| | | | | | |
Co-authored-by: Ross Barnowski <rossbar@berkeley.edu>
|
| | | | | | |
| | | | | |
| | | | | | |
Co-authored-by: Ross Barnowski <rossbar@berkeley.edu>
|
| | | |_|/ /
| |/| | | |
|
| |\ \ \ \ \
| | | | | |
| | | | | | |
BLD: Remove unused pip install
|
| |/ / / / / |
|
| |\ \ \ \ \
| | | | | |
| | | | | | |
DOC: edit to the documentation of lib/polynomial.py/polyfit
|
| |/ / / / /
| | | | |
| | | | |
| | | | |
| | | | | |
Edited the documentation of polyfit.
The scaling factor of the covariance matrix in the description was erroneous, the correct form is chi2/dof.
The code already used this correct scaling, just the description needed to be updated.
|
| |\ \ \ \ \
| | | | | |
| | | | | | |
BUG: Update compiler check for AVX-512F
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
gcc-4.9 is missing a few AVX-512F intrisics, see
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61878. We use some of these
missing intrinsics to check for compiler support of AVX-512F.
|
| |\ \ \ \ \ \
| | | | | | |
| | | | | | | |
BLD, MAINT: Pin setuptools
|
| | | | | | | | |
|
| | | | | | | | |
|
| | |/ / / / / |
|
| |\ \ \ \ \ \
| | | | | | |
| | | | | | | |
TST, MAINT: fix the test for ``np.ones``
|
| | | | | | | | |
|
