| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|\ \ \
| | | |
| | | | |
BUG: Fixes histogram monotonicity check for unsigned bin values
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
Double-indexing is just a little harder to read
|
|\ \ \ \
| | | | |
| | | | | |
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.
|
| | | | |
| | | | |
| | | | |
| | | | | |
[skip ci]
|
|\ \ \ \ \
| | | | | |
| | | | | | |
MAINT: struct assignment "by field position", multi-field indices return views
|
| | | | | | |
|
|\ \ \ \ \ \
| |/ / / / /
|/| | | | | |
DOC: Fixed doc example of apply along axis with 3D return
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
[skip ci]
|
|/ / / / /
| | | | |
| | | | |
| | | | | |
Check that axes with non-zero padding are non-empty.
|
| | | | | |
|
|\ \ \ \ \
| | | | | |
| | | | | | |
DOC: rot90 wrongly positioned versionadded directive.
|
| | | | | | |
|
|/ / / / / |
|
|\ \ \ \ \
| | | | | |
| | | | | | |
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
|
| | | | | |
|
| | | | |
| | | | |
| | | | | |
We need to find the index which is not the same with the left and right, I think np.logical_and's meaning is more clear and I test this got a speed up
|
|\ \ \ \ \
| | | | | |
| | | | | | |
Remove unittest dependencies
|
| | | | | | |
|
| | | | | | |
|
|/ / / / /
| | | | |
| | | | |
| | | | | |
This isn't the case for `diff`
|
|\ \ \ \ \
| | | | | |
| | | | | | |
ENH: Rearrange testing module to isolate nose dependency.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
The aim here is to separate out the nose dependent files prior to adding
pytest support. This could be done by adding new files to the general
numpy/testing directory, but I felt that it was to have the relevant
files separated out as it makes it easier to completely remove nose
dependencies when needed.
Many places were accessing submodules in numpy/testing directly, and in
some cases incorrectly. That presented a backwards compatibility
problem. The solution adapted here is to have "dummy" files whose
contents will depend on whether of not pytest is active. That way the
module looks the same as before from the outside.
In the case of numpy itself, direct accesses have been fixed. Having
proper `__all__` lists in the submodules helped in that.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Also remove redundancy between the function and return value descriptions
[ci skip]
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
BUG: recfunctions fail in a bunch of ways due to using .descr
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Once again, thanks to not using .descr
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
This change shouldn't affect behaviour - all old uses were still correct.
|