| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
| |
| |
| |
| |
| |
| |
| | |
The other similar arguments in the testing functions and `np.array_equal`
use `equal_nan` and not `equal_nans` (with plural s). So it seems we
should use that here as well for consistency.
Does some very minor style fixes otherwise.
|
| |
| |
| | |
Co-authored-by: Matti Picus <matti.picus@gmail.com>
|
| |
| |
| | |
Co-authored-by: Matti Picus <matti.picus@gmail.com>
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| | |
Co-authored-by: Matti Picus <matti.picus@gmail.com>
|
| | |
|
| |
| |
| | |
Co-authored-by: Robert Kern <robert.kern@gmail.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The first lines of the sinc docstring did not mention the behavior
when the argument is zero, and gave the impression that the function is
defined as the quotient between a sine and its argument everywhere. That
information was instead relegated to the "Notes" section. I found this
issue while navigating the documentation for jax.numpy.sinc, which
inherits those few lines. I think it is important to document not only
the value of the function at zero, but also that it make sinc a smooth
function. This connects better with some of the other routes used to
introduce sinc (e.g. as a Taylor series). I have tried to implement
the conclusions of the discussion around Issue #21538, keeping the
description close to the actual implementation and avoiding my original
suggestion of introducing the function as a limit.
|
|\ \
| | |
| | |
| | |
| | | |
seberg/fix-void-cast-safety-promotion-and-comparison
API: Fix structured dtype cast-safety, promotion, and comparison
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This PR replaces the old gh-15509 implementing proper type promotion
for structured voids. It further fixes the casting safety to consider
casts with equivalent field number and matching order as "safe"
and if the names, titles, and offsets match as "equiv".
The change perculates into the void comparison, and since it fixes
the order, it removes the current FutureWarning there as well.
This addresses https://github.com/liberfa/pyerfa/issues/77
and replaces gh-15509 (the implementation has changed too much).
Fixes gh-15494 (and probably a few more)
Co-authored-by: Allan Haldane <allan.haldane@gmail.com>
|
| | | |
|
| | | |
|
| | | |
|
|\ \ \
| | | |
| | | | |
TYP: Add typing for the keepdims param. of 'average' and 'ma.average'
|
| | | |
| | | |
| | | |
| | | | |
This is a follow-up to gh-21485.
|
|/ / /
| | |
| | |
| | |
| | |
| | | |
Closes gh-9982.
(Plus a few small PEP 8 fixes.)
|
| | | |
|
|/ / |
|
| |
| |
| |
| |
| |
| |
| |
| | |
Optimizes the parsing of shape tuples and integers by avoiding multiple conversions and generally
refactoring the code.
Closes gh-19010, that parsing a single integer was very slow (due to trying to convert it to a squence twice).
Co-authored-by: Sebastian Berg <sebastian@sipsolutions.net>
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
* Changed product computing logic for kron to use broadcasting
|
|\ \
| | |
| | | |
ENH: Masked Array support for `np.kron`
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
* Added `mat` cases to smoke tests
* Changed type checks to handle new change which uses ufuncs order for
result determination
* Added cases for `ma` to check subclass info retention
|
| | |
| | |
| | |
| | |
| | |
| | | |
* Replace `*` call with `multiply`
* Handle `mat` cases to perform reshape
* Remove use result wrapping to maintain consistency with ufuncs
|
|\ \ \
| | | |
| | | | |
DOC: Add space after argument name
|
| | | | |
|
| |/ / |
|
|/ / |
|
|\ \
| | |
| | | |
BUG: Fixes `ValueError` in `np.kron`
|
| | |
| | |
| | |
| | | |
Input such as matrix will cause a `ValueError` due to dim restrictions
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
* Smoke tests to ensure `np.kron` works.
* Shape tests to check if `np.kron` computes the right shape for
different edge cases of input arrays
|
| | |
| | |
| | |
| | |
| | |
| | | |
* `np.kron` uses `np.concatenate` which fails when shape is 0 along an
axis
* Refactor shape normalising portion.
|
|\ \ \
| |/ /
|/| | |
MAINT: Split `numpy.typing` into a public and private component
|
| | |
| | |
| | |
| | | |
i.e. `numpy.typing` and `numpy._typing`
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| | |
- improper urls
- a few use of single bakcticks where many are expected
- Proper numpydoc format
[ci skip]
[skip azp]
[skip circle]
|
| | |
|
|\ \
| | |
| | | |
MAINT: extend delete single value optimization
|
| | | |
|
| |\ \ |
|
| | | |
| | | |
| | | | |
Co-authored-by: Eric Wieser <wieser.eric@gmail.com>
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Allow arrays of shape (1,) for delete's obj parameter to utilize the
optimization for a single value. See #16685.
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
When the delimiter is None and we are splitting on whitespace,
a final empty field is always ignored to match the behaviour
of pythons split: `" 1 ".split()`.
Closes gh-21052
|