| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
BLD: enabled negation of library choices in NPY_*_ORDER
When users build for a particular order it may be beneficial
to disallow certain libraries.
In particular a user may not care about which accelerated
BLAS library is used, so long as the NetLIB or ATLAS library isn't used.
This is now possible with:
NPY_BLAS_ORDER='^blas,atlas'
or
NPY_BLAS_ORDER='!blas,atlas'
Since we may envision more BLAS/LAPACK libraries to the pool, this
will provide greater flexibility as they enter.
A new (local) method is added in system_info.py which removes duplicate
code and allows for easier usage across libraries.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* ENH: Allow genfromtxt to unpack structured arrays
genfromtxt failed to transpose output when
unpack=True and `dtype` was structured (or None).
This patch resolves the issue by
returning a list of arrays, as in `loadtxt`.
Co-authored-by: Matti Picus <matti.picus@gmail.com>
Co-authored-by: Eric Wieser <wieser.eric@gmail.com>
Co-authored-by: Sebastian Berg <sebastian@sipsolutions.net>
Co-authored-by: Ross Barnowski <rossbar@berkeley.edu>
|
|
|
|
| |
[skip ci]
|
|\
| |
| | |
ENH: Implement concatenate dtype and casting keyword arguments
|
| |
| |
| | |
Co-authored-by: Matti Picus <matti.picus@gmail.com>
|
| |
| |
| |
| |
| |
| |
| | |
Unfortunately, the casting was not consistent and sometimes used
force casting (axis=None) while normally same kind casting was used.
This thus deprecates the `force_casting` corner case, so that
casting has to be provided in the future.
|
|/
|
|
| |
The "do not use" comment has been here since bb0e4f356cce2f199d9c08ffe572fbabadc846d1.
|
| |
|
|\
| |
| | |
API: Remove `np.ctypeslib.ctypes_load_library`
|
| |
| |
| |
| |
| |
| | |
This function has been deprecated since fcee1ad856089a7ecb7b6865d280c0273dacb638 (Numpy v1.0b3).
14 years is more than enough time for users to switch from it.
|
|\ \
| |/
|/| |
MAINT, BUG: Remove uses of PyString_FromString.
|
| |
| |
| |
| |
| |
| |
| |
| | |
We no longer need to use the compatibility function after dropping
support for Python 2.7. In some cases unicode was the correct string
type rather than the bytes of the compatibility version and bugs in the
array `__complex__` and array `__array_interface__` methods have been
fixed by changing that.
|
|\ \
| | |
| | | |
MAINT: Revert boolean casting back to elementwise comparisons in `trim_zeros`
|
| |/ |
|
|\ \
| | |
| | | |
MAINT: Add error return to all casting functionality and NpyIter
|
| | | |
|
| |/ |
|
|\ \
| | |
| | | |
BUG: linspace should round towards -infinity
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | | |
reword the release note
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
* ENH: Add file like support to np.core.records.fromfile (#2504)
Co-authored-by: Ross Barnowski <rossbar@berkeley.edu>
|
| |/
|/|
| |
| |
| |
| |
| |
| |
| | |
As explained in NEP 32, the financial functions are to be removed
from version 1.20.
They are now replaced with module level `__getattr__` to give a useful
error message for those surprised by the `AttributeError`.
This only works for Python 3.7+, but it is expected that by the 1.20 release
Python 3.6 will not be supported.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Previously the logic assumed that an index was valid if the size was the same
as the indexed array, rather than the shape. This resulted in an index being
incorrectly allowed if the index was all False, like np.empty((3, 3))[np.full((1, 9),
False)], or incorrectly giving a ValueError about broadcasting if the index
was not all False (like np.empty((3, 3))[np.full((1, 9), True)]). Now these
examples both give IndexError with the usual error message.
Fixes #16997.
|
| |
| |
| | |
* Create copy of numpy.pxd for Cython 3.0 changes and improve it.
|
|/
|
|
|
|
|
|
|
|
|
|
|
| |
* Added a benchmark for `trim_zeros()`
* Improve the performance of `np.trim_zeros()`
* Increase the variety of the tests
Fall back to the old `np.trim_zeros()` implementation if an exception is encountered.
Emit a `DeprecationWarning` in such case.
* DEP,REL: Added a deprecation release note
|
|
|
|
|
|
|
| |
Set readonly flags in array interface dict and array struct
capsule returned by an array with warn_on_write flag set
instead of producing a deprecation warning.
Closes #16335
|
|
|
|
| |
Issue #16481
|
|\
| |
| | |
BUG: fix mgrid output for lower precision float 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.
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The kwarg option norm=inverse leads to scaling of the transforms
inverse (opposite) to that of the default option norm=None; i.e. the
forward transform is normalized with 1/n whereas the backward one
with 1. The fft routines and their tests have been modified to
reflect the changes; all tests have been passed successfully.
Closes #16126
* modified _unitary, fft & ifft and their tests; tests passed
* modified rfft & irfft and their tests; tests passed
* modified hfft & ihfft and all tests; all modifications are now done
* correction in ihfft; all 79 fft tests passed successfully
* undo unnecessary docstrings changes made in my previous commits
* use norm=forward kwarg value name
* Update numpy/fft/__init__.py
Co-authored-by: Leo Fang <leofang@bnl.gov>
* add code review suggestions
Co-authored-by: Leo Fang <leofang@bnl.gov>
* add default norm=None alias norm=backward
* streamline private normalization functions
* modify hermitian FFTs
* add review suggestions
Co-authored-by: Leo Fang <leofang@bnl.gov>
* add review suggestions v2 (dict as module const)
* make review suggestions v3
* Apply suggestions from code review
Co-authored-by: Leo Fang <leofang@bnl.gov>
|
|
|
| |
Co-authored-by: Hameer Abbasi <einstein.edison@gmail.com>
|
|
|
| |
Co-authored-by: Anirudh Subramanian <anirudh2290@apache.org>
|
|
|
|
|
|
|
|
| |
string is too short
this retains (and slightly expands) the old behaviour. It is inconsistent
and I think we should fix that inconsistency one way or the other
(I honestly do not care *which* way).
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* MAINT: Remove nickname from polynomial classes.
The convenience classes derived from ABCPolyBase had a nickname
attribute that was only used internally in the previous
implementation of __str__. After the overhaul of __str__ in #15666,
this attr is no longer used.
* DOC: Add release note.
Add release note to notify users of removal of the abstract
property, and highlight users that may be affected by the
change.
* DOC: fixed rST in release note
|
| |
|
| |
|
|\
| |
| | |
ENH: enable multi-platform SIMD compiler optimizations
|
| | |
|
|\ \
| | |
| | | |
ENH: make typing module available at runtime
|
| | | |
|
|\ \ \
| | | |
| | | | |
DEP: Deprecate aliases of builtin types in python 3.7+
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This:
* Makes accessing these attributes emit a deprecation warning
* Removes them from `dir(numpy)`, so as not to emit warnings for user of `inspect.getmembers`
These aliases are a continual source of confusion for beginners, and are still often used by accident by experts.
|
| |/
|/|
| |
| |
| |
| | |
See https://github.com/numpy/numpy/pull/16558#issuecomment-643679096.
It was previously an "improvement".
|