| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| | |
DOC: Fix for building with sphinx 3
|
| | |
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* ENH,API: Store exported buffer info on the array
This speeds up array deallocation and buffer exports, since it
removes the need to global dictionary lookups. It also somewhat
simplifies the logic. The main advantage is prossibly less the
speedup itself (which is not large compared to most things that
happen in the livetime of an array), but rather that no unnecessary
work is done for shortlived arrays, which never export a buffer.
The downside of this approach is that the ABI changes for anyone
who would be subclassing ndarray in C.
* MAINT: Do not tag the NULL (no buffers exported)
The allocation is not the right place to initialize to anything but
NULL, so take the easy path and do not tag the NULL default.
* TST: Add test for best try RuntimeError on corrupt buffer-info
* Remove NPY_SIZEOF_PYARRAYOBJECT and add some documentation
* Use 3 to tag the pointer and object for a "bad" one in the test
* DEP: deprecate the NPY_SIZEOF_PYARRAYOBJECT macro
* Tune down matti's deprecation to write the error instead.
* Tweak macro, so that clang hopefully doesn't complain.
* Use None instead of NULL in PyErr_WriteUnraisable, pypy seems to have a bug with it
* Just comment it out...
* Apply suggestions from code review
Co-authored-by: Matti Picus <matti.picus@gmail.com>
Co-authored-by: mattip <matti.picus@gmail.com>
|
|
|
| |
Co-authored-by: Eric Wieser <wieser.eric@gmail.com>
|
| |
|
| |
|
|\
| |
| | |
DOC: Fix the references for ``__array_*__``
|
| | |
|
|\ \
| | |
| | | |
DOC: Replace ``PyCObject`` with ``PyCapsule``
|
| |/ |
|
|\ \
| | |
| | | |
DOC: Add ``identity_value`` to ``PyUFuncObject``
|
| |/ |
|
|/ |
|
| |
|
| |
|
|\
| |
| | |
DOC: Add the entry for ``NPY_FEATURE_VERSION``
|
| | |
|
| | |
|
|/ |
|
| |
|
|
|
| |
`.. c:function::` expects its contents to be a valid C prototype, meaning the return types and arguments are all need types.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|\
| |
| | |
DOC: Improve documentation of C code
|
| | |
|
| | |
|
| | |
|
|/
|
| |
* DOC: Fix the declarations of C fuctions
|
|
|
|
|
|
| |
Add documentation for `PyArray_ContiguousFromObject` similar to the other
macros wrapping `PyArray_FromAny`
Fixes #16196
|
| |
|
|
|
| |
Add missing closing brackets, script to generate the list in the PR gh-16051.
|
| |
|
|
|
|
|
| |
types (#15816)
Cleanup from the dropping of python 2
|
|
|
|
|
| |
* DOC: fix coremath.rst to fix refguide_check
Co-authored-by: Eric Wieser <wieser.eric@gmail.com>
|
|\
| |
| | |
DEP: Schedule unused C-API functions for removal/disabling
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This function provides mainly the same API as PyObject_Call()
with the exception of skipping ufunc overrides and output array
wraps.
It is fairly unwieldy to use, since ownership of all inputs and
outputs is transferred, but otherwise it still uses args and kwargs
as inputs.
As such, no known usage exists and PyObject_Call seems a reasonable
replacement for possible usage. Keeping it around means that we would
may have to add tests or risk breaking this function when ufunc
code is refactored.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The function has no known usage outside of NumPy. It is fairly
complex to use due to how it behaves with scalars, and, at least
with a given "flexible" dtype would require additional access
to the private PyArray_AdaptFlexibleDType function.
Removing the function from public API will simplify refactor work
of the dtype and dimension recovery.
|
|/
|
|
|
| |
This PR const qualifies the dimension and strides arguments of PyUFuncGenericFunction. Const qualified arguments make it simpler to reason about the behaviour of these ufuncs and prevents accidental mutation. As the const is now required this PR also const qualifies calls to PyUFuncGenericFunction inside the NumPy source code.
This closes #15252
|
|\
| |
| | |
API: remove undocumented use of __array__(dtype, context)
|
| | |
|
| |
| |
| |
| |
| | |
This adds the additional deprecation of fastclip if it is set at
registration time instead of only testing that it is never used.
|
|\ \
| | |
| | | |
MAINT,API: ignore and NULL fasttake/fastputmask ArrFuncs slots
|
| |/ |
|
|/ |
|