| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
| |
Otherwise Numpydoc does not see the section.
|
| |
|
|\
| |
| | |
SIMD, TEST: Workaround for misaligned stack GCC BUG ABI on WIN64
|
| |
| |
| |
| |
| |
| | |
This patch fixes the segfault error for GCC SIMD module builds on WIN64,
the problem occurs when GCC aligned load the AVX registers(256-bit) from stack
pointer with 128-bit alignment.
|
|/
|
|
|
|
| |
- `comments`: Added a full stop after 'discarded'.
- `names`: changed 'proceeded' to 'preceeded'.
- `excludelist`: inserted 'with' because it sounds odd without it; the example makes it clear.
- `replace_space`: should strictly be "variable names" or "variables' names". The latter seems fussy so I chose the former.
|
|\
| |
| | |
ENH: Add `__all__` to a number of public modules
|
| | |
|
| |
| |
| |
| | |
All new function definitions based on the respective functions' docstring
|
|/
|
|
|
| |
Use explicitly defined classes rather than annotating them as `Type[Any]`.
The latter currently causes issues with mypy, which does not allow it to be used as a baseclass (because reasons?)
|
| |
|
| |
|
| |
|
|
|
|
| |
Change `int` into the more forgiving `SupportsIndex` protocol
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
instead of `import numpy.testing as npt`.
- all of NumPy's own tests themselves use the from-import variant
- There's `import numpy.typing as npt` around in some places so
we should not abbreviate another module import with `npt`.
Optional further enhancement: If this is a convention we also want
users to adopt, this should be mentioned in the module docstring of
`numpy.testing`.
|
|
|
|
| |
It has been deprecated and removed for quite some time
|
| |
|
| |
|
| |
|
|
|
|
| |
e.g. types and instances
|
|\
| |
| | |
API, DEP: Move ufunc signature parsing to the start
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This may have slight affects on users, see release notes.
Mainly, we have to parse the type tuple up-front (because we need
to replace the current type resolution). Since we _must_ de-facto
replace the current type resolution, I do not see why we should
duplicate code for the odd possibility of someone actually calling
`ufunc.type_resolver()` with a `typetup` that is not a actually a
type tuple.
This commit also deprecates `signature="l"` as meaning (normally)
the same as `dtype="l"`.
|
|\ \
| | |
| | | |
MAINT: Add exception chaining where appropriate
|
| | | |
|
| | | |
|
| |\ \
| | | |
| | | |
| | | | |
avo-exceptions-chaining
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | | |
MAINT: Add exception chaining where appropriate
|
| | | | | |
|
| | | | | |
|
| |\ \ \ \ |
|
| | | | | |
| | | | | |
| | | | | | |
Co-authored-by: Eric Wieser <wieser.eric@gmail.com>
|
| |/ / / / |
|
| | | | | |
|
|\ \ \ \ \
| | | | | |
| | | | | | |
BUG: Regression #18075 | Fixing Ufunc TD generation order
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Fixes https://github.com/scipy/scipy/issues/11339
**What does this implement/fix?**
NumPy/SciPy compiled with Intel Fortran compiler using default flags treats both -0.0 and +0.0 as 0.0, however it is not IEEE 754 compliant and some SciPy logic relies on this -0.0 and +0.0 differentiation.
|
|/ / / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
The test_operator_object_left and test_operator_object_right tests in
test_scalarmath.py set a maximum recursion depth of 100 that caused an
error in gitpod because it was too close to the starting depth of 75.
The fix here is to raise the maximum depth to 200.
Closes #18749
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
(#18737)
This enables the behaviour of the build honouring the environment
variables NPY_BLAS_LIBS, NPY_CBLAS_LIBS, and NPY_LAPACK_LIBS
to select any standard-conforming implementation of the f77
interfaces.
This is needed to sanely have automated builds provide BLAS libs
in a way common to multiple packages (using some environment variable,
BLAS_LIBS being canonical, but variants exist). Hacking a site.cfg
is fine for a single user, but does not scale well. As example,
pkgsrc, the NetBSD packages collection, offers differing builds
of Netlib or OpenBLAS, the latter in variables openblas,
openblas_openmp, and openblas_pthread. With this patch, differing
builds can just use different variable values like
NPY_BLAS_LIBS=-lblas NPY_CBLAS_LIBS=-lcblas \
NPY_LAPACK_LIBS='-lapack -lblas' \
python setup.py build
NPY_BLAS_LIBS=-lopenblas_pthread NPY_CBLAS_LIBS= \
NPY_LAPACK_LIBS='-lopenblas_pthread' \
python setup.py build
(NPY_LAPACK_LIBS contains reference to BLAS, too, for packages that only
use LAPACK and would miss underlying BLAS otherwise for static linking.)
|
| |_|_|/
|/| | |
| | | |
| | | |
| | | | |
* DOC: Emphasize distinctions between np.copy and ndarray.copy
Co-authored-by: Melissa Weber Mendonça <melissawm@gmail.com>
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Check that out is C-contiguous when using user-supplied arguments
closes #18704
|
|\ \ \ \
| | | | |
| | | | | |
ENH, SIMD: Dispatch for unsigned floor division
|
| | | | |
| | | | |
| | | | | |
Co-authored-by: Sayed Adel <seiko@imavr.com>
|