| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|\
| |
| | |
BUG: Fix memmap regression when shape=None
|
| | |
|
| | |
|
|\ \
| |/
|/| |
BUG: Revert multifield-indexing adds padding bytes for NumPy 1.15.
|
|/ |
|
|\
| |
| | |
BUG: Undo behavior change in ma.masked_values(shrink=True)
|
|/
|
|
|
|
| |
This change was introduced as part of #10232
Fixes #11112
|
|\
| |
| | |
BUG: Fix segfault on failing __array_wrap__
|
| | |
|
|\ \
| | |
| | | |
DOC: fix hierarchy of numericaltype
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Code documentation did not make clear the hierarchy for the types
`number`, `integer`, `unsignedinteger`, `signedinteger`,
`flexible`, `character`, and `void`; and their subdtypes.
This edit adds additional indentation and arrows in the
documentation style to indicate the type hierarchy.
This edit also adjusts whitespaces to align columns of
additional information (alises and kind shorthands) in the
documented hierarchy.
|
| | |
| | |
| | |
| | |
| | |
| | | |
Code documentation of numpy scalar types indicated the wrong type
(number) for the kind 'i'. This edit moves the indication to the
right type (unsignedinteger).
|
|\ \ \
| | | |
| | | | |
MAINT: Do proper cleanup in get_ufunc_arguments.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Instead of leaving it to the caller to clean up references
to operands.
|
|\ \ \ \
| |_|/ /
|/| | | |
BUG: Remove extra trailing parentheses.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The `npy_get_floatstatus_barrier` had an extra parentheses in the
argument list of the function definition that was exposed when compiling
on NetBSD.
Closes #11288.
|
|\ \ \ \
| |/ / /
|/| | | |
DOC: Make reference doc nditer examples python3 friendly
|
| | | | |
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | | |
DOC: Minor documentation improvements
|
| | | | | |
|
|/ / / / |
|
|\ \ \ \
| | | | |
| | | | | |
BUG: Remove invalid read in searchsorted if needle is empty
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
The tests are a bit ugly, but the cache otherwise hides the errors
away during testing.
The ternary operation did not work, because complex types do not like
assignment of 0.
Closes gh-11261
|
|\ \ \ \ \
| | | | | |
| | | | | | |
BUG: Work around past and present PEP3118 issues in ctypes
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
np.dtype(type(ctype_obj))
Fixes gh-10528
Fixes gh-10978
Fixes gh-11150
A warning is thrown when ctypes misbehaves, in order to not hide issues that need fixing upstream
|
| | | | | | |
|
| | |_|_|/
| |/| | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
* update docstring of interp()
* change "calculate" to "evaluate" to be consistent
* remove "values"
* make "data points" consistent
|
|\ \ \ \ \
| |/ / / /
|/| | | | |
BUG: Prevent stackoverflow in conversion to datetime types
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | | |
Fixes gh-11154
|
|\ \ \ \ \
| | | | | |
| | | | | | |
BUG: Set ndarray.base before __array_finalize__
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Fixes #11237
Without this, we expose arrays to python before the lifetime of their buffer has been correctly attached, which can lead to use-after-frees (see the referenced issue).
Unfortunately, this means that `PyArray_SetBaseObject(arr, base)` is still broken in downstream code for any cases where `arr.__array_finalize__ is not None`. We may have no choice but to deprecate this function, and expose PyArray_FromDescrAndBase. But lets leave fixing public API to a later date...
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Also move an assignment ouf of an if.
Only targeting calls that then go on to call PyArray_SetBaseObject
|
|\ \ \ \ \ \
| |_|_|_|_|/
|/| | | | | |
TST: Do not use empty arrays in tests (unless they are not read)
|
| | |_|/ /
| |/| | |
| | | | |
| | | | |
| | | | | |
Not initializing arrays throws off valgrind, so avoid it here. For a while
I thought it was just a false positive due to some SSE string compare function.
|
|\ \ \ \ \
| | | | | |
| | | | | | |
WIP: Remove fragile use of __array_interface__ in ctypeslib.as_array
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Everything behaves a lot better if we let the array constructor handle it, which will use the ctypes PEP3118 support.
Bugs this fixes:
* Stale state being attached to pointer objects (fixes gh-2671, closes gh-6214)
* Weird failure modes on structured arrays (fixes-10978)
* A regression in gh-10882 (fixes gh-10968)
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
ENH: Implement axis for generalized ufuncs.
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Much faster, and much less code duplication than I feared.
|
| | | | | | | |
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Both in the general documentation and in the release notes.
|