| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| | |
ENH: Add namedtuple return types to linalg functions that return tuples
|
| | |
|
| |
| |
| | |
Co-authored-by: Bas van Beek <43369155+BvB93@users.noreply.github.com>
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
That is, eig(), eigh(), qr(), slogdet(), and svd(). For those functions that
return non-tuples with certain keyword arguments, the return type is
unchanged. This change should be completely backwards compatible.
The namedtuple attribute names come from the array API specification (see,
e.g.,
https://data-apis.org/array-api/latest/extensions/generated/signatures.linalg.eigh.html),
with the exception of eig() which is just the same as eigh(). The name of the
namedtuple object itself is not part of the specification or the public API.
I have not used a namedtuple for the tuple output for qr(mode='raw'), which
returns (h, tau).
This updates the docstrings to use the updated namedtuple return names, and
also the examples to use those names more consistently. This also updates the
tests to check each function for the namedtuple attributes at least once.
|
|\ \
| | |
| | | |
BUG: Use 2GiB chunking code for fwrite() on mingw32/64
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This is a bit too broad because msys UCRT runtime may actually not
need it. Changes the type in the loop to `size_t`. This is not necessary
but the current constants are buggy without it if the branch is accidentally
used on 32bit.
|
| | |
| | |
| | |
| | | |
Addresses #2256
|
|\ \ \
| | | |
| | | | |
BUG: Fix weak scalar logic for large ints in ufuncs
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
This fixes it, breaks warnings (partially), but most or all of
those paths should be errors anyway.
|
|\ \ \ \
| | | | |
| | | | | |
ENH: Restore TypeError cleanup in array function dispatching
|
| | | | |
| | | | |
| | | | |
| | | | | |
Not that it mattered, but docs say direction should be either -1 or 1
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
When the dispathcer raises a TypeError and it starts with the dispatchers
name (or actually __qualname__ not that it normally matters), then it is
nicer for users if we just raise a new error with the public symbol name.
Python does not seem to normalize exception and goes down the unicode path,
but I assume that e.g. PyPy may not do that. And there might be other
weirder reason why we go down the full path. I have manually tested it
by forcing Normalization.
Closes gh-23029
|
| | | | | |
|
| | | | | |
|
|\ \ \ \ \
| | | | | |
| | | | | | |
ENH: Speed up 64-bit qsort by 1.6x
|
| | |/ / /
| |/| | | |
|
|\ \ \ \ \
| |/ / / /
|/| | | | |
MAINT: do not use copyswapn in array sorting internals
|
| | | | | |
|
|\ \ \ \ \
| | | | | |
| | | | | | |
DOC: Rewrite docstrings of `ogrid` and `mgrid`
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Removed references to `nd_grid` instead of adding a document (gh-23612).
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This is fallout from https://github.com/cython/cython/pull/5386
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Remove `find_common_type` export from `numpy/__init__.pyi`.
|
|\ \ \ \ \ \ |
|
| |\ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
ENH: add fast path for str(scalar_int)
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
* BUG: properly handle tuple keys in NpZFile.__getitem__
* TST: test tuple rendering specifically.
---------
Co-authored-by: Ross Barnowski <rossbar@berkeley.edu>
|
| |\ \ \ \ \ \ \
| | | | | | | | |
| | | | | | | | | |
BUG: Fix crackfortran groups for endifs with comments
|
| | | | | | | | | |
|
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
Harmonizes patterns a bit as well
|
| | | | | | | | | |
|
| |/ / / / / / / |
|
| |\ \ \ \ \ \ \
| | | | | | | | |
| | | | | | | | | |
MAINT, BLD: Disable spr for clang
|
| | |/ / / / / /
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Clang has a bug and fails when compiling
`simd_qsort_16bit.dispatch.avx512_spr.cpp`
Closes #23730.
|
| | |_|/ / / /
| |/| | | | | |
|
| |\ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
DOC: Add symbol in docstring for classes derived from ABCPolyBase
|
| | |/ / / / /
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
A 'symbol' argument was added in ABCPolyBase in 1.24 and documented there, but
the docstrings for derived classes (e.g., Polynomial) were not updated.
|
| |\ \ \ \ \ \
| | |/ / / / /
| |/| | | | | |
MAINT: Add a proper implementation for structured zerofill
|
| | | | | | | |
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
This reorganizes the generic traversal functions for structured
dtypes a bit (before it wasn't quite generic).
Then uses that for zerofilling. We could get the two a bit closer
by also supporting `func==NULL` explicitly for clearing.
(I have not includes this here.)
The old `FillObjectArray` is still in use now, this is not ideal
and the new approach should be duplicated to add an "emptyfill"
(same semantics, normally just memset to 0, but for objects we
place an explicit `None` object).
This is a necessary follow-up to gh-23591.
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
BufferedReader and BufferedWriter cannot be used to determine local
files. For example, users can implement CustomFile to operate on OSS
files, and then use BufferedReader(CustomFile) to achieve the buffered
effect. But fileno method can do it.
|
| |\ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
MAINT: Reorganize the way windowing functions ensure float64 result
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
This roughly changes things so that we ensure a float64 working
values up-front. There is a tiny chance of precision changes if the
input was not float64 or error changes on bad input.
I don't think this should matter in practice, precision changes
(as far as I can tell) should happen rather the other way around.
Since float64 has 53bits mantissa, I think the arange should give
the correct result reliably for any sensible inputs.
There is an argument to be made that the windowing functions could
return float32 for float32 input, but I somewhat think this is OK
and users can be expected to just cast manually after the fact.
The result type is tested, but this ensures the tests pass also
when enabling weak promotion.
|
| | | | | | | | |
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
xref https://github.com/numpy/numpy/pull/23358
|