| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |/
| |
| |
| |
| |
| |
| |
| | |
1. PyArray_CopyObject
2. PyArray_MapIterArray
3. PyArray_MapIterSwapAxes
4. PyArray_MapIterNext
5. PyArray_MapIterArrayCopyIfOverlap
|
|/ |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
* Created fundamentals doc for explanations in ufunc reference doc
* Move explanatory material on ufuncs and broadcasting from the
reference guide to the ufunc fundamentals and/or broadcasting
document in the user guide
* Added examples for ufunc method arguments
* Reorganized broadcasting duplicate content from ufuncs doc
Co-authored-by: Melissa Weber Mendonça <melissawm@gmail.com>
|
| |
|
| |
|
|\
| |
| | |
MAINT: Refactor UFunc core to use NEP 43 style dispatching
|
| |
| |
| |
| | |
Co-authored-by: Matti Picus <matti.picus@gmail.com>
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The first (big) chunk of a multi-step process to update all ufuncs
to NEP 43 style ufuncs.
This limits itself to normal ufunc calls and sets ufunc.at and
all reduce-like operations to the side. These would add another
level of complexity.
|
| |
| |
| | |
Co-authored-by: Matti Picus <matti.picus@gmail.com>
|
| |
| |
| |
| | |
PyArray_FinalizeFunc.
|
| | |
|
|/ |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This PR adds the new axis and ndim attributes to the np.AxisError class, an addition inspired by similar
changes introduced to AttributeError in Python 3.10.
It also provided an excuse to update the classes' documentation and tests, both of which were previously rather lacking.
* ENH: Add the `axis` and `ndim` attributes to `np.AxisError`
* MAINT: Let the new `AxisError` attributes survive pickling
* DOC: Update the `AxisError` documentation
* TST: Update the `AxisError` tests
* DOC: Add a release note
* MAINT: Improve the description of `AxisError`s overloaded constructor
* TST: Fix a few typing test failures
* DOC: Clarify a fix a few parts of the `AxisError` docstrings
Co-Authored-By: Eric Wieser <425260+eric-wieser@users.noreply.github.com>
* DOC: Reguide fix
* DOC: Replace `versionadded` with `versionchanged`
Co-authored-by: Eric Wieser <wieser.eric@gmail.com>
* DOC: Mention that `AxisError` is a `ValueError` and `IndexError` subclass
Co-Authored-By: Sebastian Berg <sebastian@sipsolutions.net>
* ENH: Delay assembling of the error message until `__str__` is called
Co-Authored-By: Eric Wieser <425260+eric-wieser@users.noreply.github.com>
* DOC: Update the `AxisError` string representation in its docstring
* DOC: Update `versionadded`-related information
Co-Authored-By: Eric Wieser <425260+eric-wieser@users.noreply.github.com>
* DOC: Fix sphinx warnings
Co-authored-by: Eric Wieser <425260+eric-wieser@users.noreply.github.com>
Co-authored-by: Eric Wieser <wieser.eric@gmail.com>
Co-authored-by: Sebastian Berg <sebastian@sipsolutions.net>
|
| |
|
|
|
|
|
| |
* MAINT: Move masked code 1:1 (does not work)
* MAINT: Fixup code move and small follow-up fixes
|
| |
|
|
|
|
|
|
| |
Document that NeighborhoodIterator will point to the begining
of the data instead of the position pointed by iter on creation
in the special case where data is contiguous.
|
|
|
| |
Fixed unsigned integer aliases.
|
|\
| |
| | |
MAINT: Implement new style promotion for `np.result_type`, etc.
|
| |
| |
| |
| |
| |
| |
| | |
This doesn't serve any purpose anymore. The new code is now always
used. (In very few cases this may lead to small slowdowns, this
should only matter in ufuncs where it doesn't seem to matter enough
to worry about it.)
|
| | |
|
| |
| |
| |
| | |
version needed for random c-api
|
| | |
|
|\ \
| |/
|/|
| |
| | |
seberg/make-signature-resolve-more-strict-and-fix-nextafter
API: Ensure that casting does not affect ufunc loop
|
| | |
|
| |
| |
| | |
Co-authored-by: Ross Barnowski <rossbar@berkeley.edu>
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Also, for now enforce *all* outputs. That is more conservative, and
obviously won't work for certain functions in scipy that have multiple
outputs of different types, but it seems a bit safer to me right now.
Maybe at some point we have an idea of how to "modify" what the `dtype`
means. I am not sure how! By allowing the ufunc itself to interpret
how to translte it to a `signature`? By giving it a distinct meaning?
Yes, this might narrow us down a bit... but...
|
|\ \
| | |
| | | |
DOC: Update performance for new PRNG
|
| | |
| | |
| | |
| | | |
Add performance benchmarks for PCG64DXSM
|
| | | |
|
| | | |
|
| | | |
|
|/ / |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
|/ |
|
| |
|
|
|
|
|
| |
DOC
Fix typo in random docs `Randomstate` -> `RandomState`
|
|\
| |
| | |
DOC: Update random c-api documentation
|
| | |
|