| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|\ \
| | |
| | | |
DOC: Fix a wrong format of reference
|
| | | |
|
|/ / |
|
| | |
|
| | |
|
|\ \
| | |
| | | |
ENH: allow using dtype classes in array creation functions
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This enables writing np.array(some_object, dtype=type(np.dtype('i'))). This
is a follow-on from https://github.com/numpy/numpy/pull/23154, see that PR
for more details.
I had to add a new include to `ctors.h` to bring in the definition of the
`npy_dtype_info` struct. Since `ctors.h` is included in many other files inside
numpy, I found that I needed to modify fewer includes across numpy if I moved
the definition of `npy_dtype_info` to `common.h` from `descriptor.h`. The new
includes of `common.h` are needed to support later includes of `ctors.h` in
those files. If anyone has an alternate place to put `npy_dtype_info` that would
cause less churn of includes I'd love to hear about it.
I spent a bunch of time tweaking the reference counts. I'm reasonably confident
this is correct but not 100%, an additional careful pass over the reference
count logic from a reviewer would be very appreciated.
I could have made `_PyArray_FromAny` and `_PyArray_CheckFromAny` take just a
`npy_dtype_info` struct, but I found it made the reference count logic more
complicated, since `PyArray_FromAny` and `PyArray_CheckFromAny` steal the
reference to the descriptor they are passed and I needed to conserve that
behavior. Also both functions support passing in a `NULL` pointer for the
descriptor and I needed to maintain that behavior as well.
The change to `ucsnarrow.h` fixes a preexisting conflict with the prototype
in `ucsnarrow.c` that triggered a compiler error while I was working on this.
|
|\ \ \
| |/ /
|/| | |
ENH: Allow ``where`` argument to override ``__array_ufunc__``
|
| | |
| | |
| | |
| | | |
override `__array_ufunc__`.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
As discussed in
https://mail.python.org/archives/list/numpy-discussion@python.org/thread/UKZJACAP5FUG7KP2AQDPE4P5ADNWLOHZ/
This flag was always meant to be temporary, and cleaning it up is
long overdue.
|
| | |
| | |
| | |
| | | |
Closes gh-13877
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The function is more commonly called `round`, both in the array API
standard and in other array libraries (e.g., PyTorch has `round` but not
around). Plus we have `ndarray.round`.
`around` is heavily used, so keep it as an alias - but prefer `round`.
For both this switch and for keeping the alias, xref gh-13877.
Closes gh-19717
|
|/ / |
|
|\ \
| | |
| | | |
API: Add `rng.spawn()`, `bit_gen.spawn()`, and `bit_gen.seed_seq`
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
Trying to address Robert Kerns review comments.
|
|\ \ \
| |/ /
|/| | |
BLD: Add compile and runtime checks for AVX512_SPR
|
| | | |
|
|/ /
| |
| |
| |
| |
| |
| | |
The idea of the flag is not to allow to change it right now, since
there may be some things where that is hard to do in general, and
it doesn't seem relevant: nobody is supposed to use it besides for
testing.
|
| |
| |
| |
| |
| |
| | |
Add link to array iterator example
Co-authored-by: arunkumarkota <arunkumarkota@gmail.com>
Co-authored-by: Arun Kota <arunkota@Aruns-iMac.local>
|
| |
| |
| | |
sizof -> sizeof
|
| |
| |
| |
| |
| |
| |
| | |
CircleCI is currently not set up to fail when docs fail, so this
slipped through the cracks.
It may be that the testing docs should get a bit more changes then
just removing these things.
|
| | |
|
| | |
|
| |
| |
| | |
Co-authored-by: Ross Barnowski <rossbar@berkeley.edu>
|
| |
| |
| | |
Co-authored-by: Ross Barnowski <rossbar@berkeley.edu>
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
* Add reshape differences to the array API compat document
* Add an item to the array API compat document about reverse broadcasting
* Make some wording easier to read
|
| | |
|
| |
| |
| |
| |
| | |
AxisError did exist, but e.g. ComplexWarning wasn't even properly
included.
|
|\ \
| | |
| | | |
API: Add numpy.testing.overrides to aid testing of custom array containers
|
| | |
| | |
| | |
| | | |
Closes #15544
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
(#22684)
* make isnan, isinf, isfinite, signbit, nextafter aliases
* fixes from review
Co-authored-by: Sebastian Berg <sebastianb@nvidia.com>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
We do not use these in NumPy anymore, and at this point the whole
`npy_interrupt.h` header only exists in case someone is using it
out there.
We may wish to just remove it at some point, vendoring the header is
simple enough after all (and no known downstream usage exists).
See also gh-7545, gh-12541
|
|\ \ \
| | | |
| | | | |
DEP: Next step in scalar type alias deprecations/futurewarnings
|
| |/ / |
|
|/ / |
|
| |
| |
| |
| |
| |
| | |
[skip azp] [skip actions]
Closes gh-21431
|
|/
|
|
|
|
| |
Add examples to char module docstring showing use-cases for a couple of the
functions in the package.
Co-authored-by: Ross Barnowski <rossbar@berkeley.edu>
|
| |
|
|\
| |
| | |
DOC: Remove documentation specific to Python 2
|
| | |
|
| | |
|
|/ |
|
| |
|
| |
|
|
|
|
|
|
|
| |
* Fix typo disutils -> distutils
* Update doc/source/reference/distutils_status_migration.rst
Co-authored-by: Melissa Weber Mendonça <melissawm@gmail.com>
|
|
|
|
|
| |
[skip github]
[skip azp]
|
|\
| |
| | |
ENH: Use `threadpoolctl` in `show_runtime` (a new function)
|