| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | | | |
|
| | | | |
|
| |_|/
|/| |
| | |
| | |
| | |
| | | |
This previously failed with:
TypeError: Cannot cast ufunc subtract output from dtype('complex128') to dtype('float64') with casting rule 'same_kind'
|
|\ \ \
| | | |
| | | | |
BUG: arrays not being flattened in `union1d`
|
| | | |
| | | |
| | | | |
[ci skip]
|
| | | | |
|
| | | | |
|
|\ \ \ \
| |/ / /
|/| | | |
MAINT: pytest cleanups
|
| | | | |
|
| |_|/
|/| |
| | | |
Found via `codespell`
|
|/ / |
|
| |
| |
| |
| | |
Currently only supported for explicit bins
|
| |
| |
| |
| |
| | |
Fixes gh-7503
Closes gh-8984
|
| |
| |
| |
| | |
Closes gh-7864
|
|\ \ |
|
| |/
| |
| |
| | |
Fixes gh-9233
|
|/
|
|
|
|
|
| |
800 self-contained lines are easily enough to go in their own file, as are the 500 lines of tests.
For compatibility, the names are still available through `np.lib.function_base.histogram` and `from np.lib.function_base import *`
For simplicity of imports, all of the unqualified `np.` names are now qualified
|
|
|
|
| |
Minor cleanups of old code to reflect more modern usage.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
This modifies loadtxt and genfromtxt in several ways intended to add
unicode support for text files by adding an `encoding` keyword to
np.load, np.genfromtxt, np.savetxt, and np.fromregex. The original
treatment of the relevant files was to open them as byte
files, whereas they are now opened as text files with an encoding. When
read, they are decoded to unicode strings for Python3 compatibility,
and when written, they are encoded as specified. For backward
compatibility, the default encoding in both cases is latin1.
|
| |
|
|
|
| |
Fixes #9995
|
|
|
|
|
| |
Adds support for Decimal to the rate, pv, fv, pmt, ppmt, ipmt, mirr, npv functions
Closes #9781
|
|
|
|
| |
Especially necessary given the strange heuristics that decay the number of conditions to 1
|
| |
|
|
|
|
|
|
| |
single boolean is ok
Also fix the test added in gh-4792, which didn't make sense, but passed anyway
|
|\
| |
| | |
DEP: 0 should be passed to bincount, not None
|
| | |
|
|/
|
|
| |
Fixes gh-580
|
|\
| |
| | |
BUG: Fixes histogram monotonicity check for unsigned bin values
|
| | |
|
|\ \
| | |
| | | |
BUG: various fixes to np.gradient
|
| | |
| | |
| | |
| | |
| | |
| | | |
2d arrays would work, but in unpredictable and undocumented ways.
This at least makes gh-9401 give a better error message.
|
| | |
| | |
| | |
| | | |
This fixes gh-8292
|
| | |
| | |
| | |
| | |
| | | |
savetxt does not support saving arrays of dimension 0 or higher than 2.
This pull request improves the message of the error raised.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Previously, saving format version 1 would align to 16 bytes,
and saving version 2 would align improperly (bug #8085).
Alignment is now always at least 64 bytes in either version,
which supports memory mapping of the saved files on Linux,
where mmap() offset must be a multiple of the page size.
Why 64 bytes? Simply because we don't know of a case where
more is needed. AVX alignment is 32 bytes; AVX-512 is 64.
Fixes #8085, closes #8598.
|
| | | |
|
| | |
| | |
| | |
| | | |
Check that axes with non-zero padding are non-empty.
|
| | | |
|
|\ \ \
| | | |
| | | | |
TST, MAINT: Add `__init__.py` files to tests directories.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This allows pytest to run with duplicate test file names. Note that
`python <path-to-test-file>` no longer works with this change, nor will
a simple `pytest numpy`, because numpy is imported from the numpy
repository. However, `python runtests.py` and `>>> numpy.test()` are
still available.
|
|/ / /
| | |
| | |
| | |
| | | |
Also add a hint to the documentation advising the use of moveaxis over rollaxis.
Tests for rollaxis are left alone.
|
|\ \ \
| | | |
| | | | |
BUG: Fix problems with obj2sctype
|
| | | | |
|
|\ \ \ \
| |/ / /
|/| | | |
BUG: issubdtype is inconsistent on types and dtypes
|
| | | | |
|
|/ / /
| | |
| | |
| | |
| | |
| | | |
I don't know what that argument was used for, but it showis up in old
tests and is not explicitly used within the tests. I assume it was part
of an old testing framework and is now longer needed.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This is the case for x in {int, bool, str, float, complex, object}.
Using the np.{x} version is deceptive as it suggests that there is a
difference. This change doesn't affect any external behaviour. The
`long` type is missing in python 3, so np.long is still useful
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
TST: Added tests for `n` parameter
Added test for `datetime64` type change
Added tests for axis normalization
Added test for subtype handling
DOC: Minor updates to docs:
Added explanation for `n==0`
Added documentation describing `datetime64` handling
Updated formatting
Added call to normalize_axis_index
|
|\ \ \
| | | |
| | | | |
Remove unittest dependencies
|