| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| |\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
DOC: Fix rst rendering in data types
|
| | | | | | | | | |
|
| | | | | | | | | |
|
| |\ \ \ \ \ \ \ \
| | | | | | | | |
| | | | | | | | | |
Fixing failure on Python 2.7 on Windows 7
|
| | |/ / / / / / /
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
When executing pytest --pyargs numpy.distuils.tests.test_fcompiler
test_fcompiler_flags fails with
```
> raise e
E ValueError: [u'path', u'include', u'lib']
lib\site-packages\numpy\distutils\fcompiler\compaq.py:100: ValueError
---------------------------- Captured stdout call -----------------------------
Unexpected ValueError in C:\TCAgent1\work\7cc6992266387eba\distribution\lib\site
-packages\numpy\distutils\fcompiler\compaq.py
```
It appears that the list argument of ValueError contains 'path' not at the
end of the list like the current test expects, but at the beginning.
After this fix, 9 test failures of `pytest --pyargs numpy.distutils` go away.
|
| |/ / / / / / /
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Quickstart guide recommends np.set_printoptions(threshold=np.nan) but that fails.
So changed that to np.set_printoptions(threshold=sys.maxsize)
Closes #13900
* DOC:Update the docstring of set_printoptions
Add preferred max value for threshold is sys.maxsize
* Revert "DOC:Update the docstring of set_printoptions"
This reverts commit 9641121fcb84b9ad5edb188a4a5b4ac9361fbf0b.
* DOC:Update the docstring of set_printoptions
Add preferred max value for threshold is sys.maxsize
* DOC:Update the docstring of set_printoptions
Better pharasing in docstring.
* DOC:Update the description of set_printoptions in quickstart doc #13900
Fix indentation
|
| |\ \ \ \ \ \ \
| |/ / / / / /
| | | | | | | |
MAINT,BUG,DOC: Fix errors in _add_newdocs
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
This caught us trying to document members that don't exist.
|
| | | | | | | | |
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
`ndarray._as_parameter_` is not a real thing
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
This must have been lost in the multiarray / umath merge.
Found by noticing that `add_newdocs` was being called on an object that does not exist.
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Avoid using `_add_newdocs` if these functions do not exist.
Leaving the version-checking here so that we can backport to 1.16
|
| | |_|/ / / /
|/| | | | |
| | | | | |
| | | | | | |
This reverts commit 7ac7fa9a4621f7392f534b20f0cdd64967e9c7eb.
|
| |\ \ \ \ \ \
| | | | | | |
| | | | | | | |
MAINT: Fix wrong spelling of ufunc
|
| | | | | | | | |
|
| |\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
DOC: Adds documentation of functions exposed in numpy namespace
|
| | | | | | | | | |
|
| | | | | | | | | |
|
| |\ \ \ \ \ \ \ \
| | | | | | | | |
| | | | | | | | | |
DOC: Remove explicit .next method calls with built-in next function calls
|
| | | |_|_|/ / / /
| |/| | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
In some cases the documentation examples failed with an
AttributeError because the next method was not there. In a
few other cases it still worked but may be more future-proof
and ideomatic if they used the next function instead of the
next method.
|
| |\ \ \ \ \ \ \ \
| |/ / / / / / /
|/| | | | | | | |
BUG: handle weird bytestrings in dtype() (#13902)
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Use the b'' constructor rather than bytes([])
|
| | | | | | | | | |
|
| | | |_|_|/ / /
| |/| | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
* Explicit check for negative type value in PyArray_DescrFromType
* PyArray_DescrConverter casts to unsigned char to match python bytes
* Add some tests
|
| |\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
MAINT: Remove unnecessary parenthesis in numpy.ma.core
|
| | |/ / / / / / |
|
| | |_|/ / / /
|/| | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
* BUG: Remove items from `multiarray.__all__` which do not exist on python 3
Avoid using `_add_newdocs` if these functions do not exist.
Leaving the version-checking here so that we can backport to 1.16
* BUG: Add missing `np.core.multiarray._get_ndarray_c_version` function
This must have been lost in the multiarray / umath merge.
Found by noticing that `add_newdocs` was being called on an object that does not exist.
* DOC: Remove documentation for property that does not exist
`ndarray._as_parameter_` is not a real thing
* DOC: Remove docstrings which are duplicated from `numpy/core/multiarray.py`
* BUG: Don't silence errors in add_newdoc caused by bad arguments
This caught us trying to document members that don't exist.
|
| |/ / / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
For array likes supporting UFuncs, `np.abs` would return an array-like,
and this is currently not compatible with the use of `np.piecewise`.
The simplest fix seems to be to just call asanyarray (which piecewise
calls anyway on the array) beforehand. This way we ensure the conditions
are also an array.
Fixes gh-13894
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
* BUG: Fix leaking of object descriptor on dtype discovery of `None`
* BUG: Fix reference count leak in string discovery code path
* BUG: Fix two more datetime related reference count bugs
One is leaking only the python integer 1, the other a descriptor.
* BUG: Fix bugs in vectorized string functions error paths
Fixes reference count issues (a leak) in
TestVecString::test_non_existent_method and
TestVecString::test_non_string_array
* BUG: Fix Reference count leak in in128 C-level tests
* BUG: Fix refcount leak in advanced indexing error path
* BUG,MAINT: Refactor indexing dtypes handling in mapiter constructor
Using borrowed references for the dtypes seems much easier to get
the reference counts right.
* BUG: Reference leaks in deprecated datetime with timezone coercion
* BUG: Refcount issue in nonzero 0-d path
* BUG: Fix ufunc.at dtype refcount handling in resolver
* BUG: Fix reference count in nditer python op_axes setup
* BUG: Reference leak in writebackifcopy non-array error path
* BUG: Add missing DECREF in ufunc with dtype type resolution
* BUG: Reference count bugs in io functions
* BUG: Reference count loss in as_c_array C-side tests
* BUG: Leaking of method in object method based ufunc loops
The function could possibly be optimized nicely by checking
that the method will be the same because the types are identical.
OTOH, that may not be correct in dynamically adapted types.
* TST: Clean up cyclic ctypes reference to simplify leak debugging
If we do not clean it up in this test, the collection can take
so long that it affects the following tests when running with
reference leak debugging tools (pytest-leaks).
* BUG: Reference count of raw data for 0-sized unpickling
* TST: Mark tests which must leak references
It really may be time to remove this, considering how annoying this
is, may want to think about getting rid of that behaviour.
Could probably write a multiearraytests C-side function instead.
* BUG: Fix refcount leaks in arr.getield and setfield error paths
* BUG: Fix refcount issue in wheremask
This fix is not the prettiest, since it relies on the wheremask
to be formatted to boolean beforehand correctly.
* TST: Reset StringConvert after mutating it in tests
Or maybe just mark the test?
* BUG: Fix missing static for npy_cache_import in umath funcs.inc.src
* BUG: Fix refcount in multiternew error path
* BUG: Fix npy_ObjectGCD and LCM reference counting
* BUG: Decrement already wrapped outputs on failure
This is not super pretty, but not sure how to do it much better
right now.
* FIXUP: iotools StringConverter._mapper
* FIXUP: as_c_array tests
* FIXUP: String/dtype discovery comment
* FIXUP: Nonzero comment
* FIXUP: mapiternew -- check error return of dtype creation
In principle, at least at this time, this is not possible
|
| |\ \ \ \ \
| | | | | |
| | | | | | |
BUG: Do not crash on recursive `.dtype` attribute lookup.
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
The code path in scalarapi.c which checks dtype on one inheriting
from np.void is especially awkward and was completely untested
previously. So I am not sure we should even support it at all.
Closes gh-12982, gh-3614, and gh-12751
|
| | |_|_|_|/
|/| | | | |
|
| | | | | | |
|
| |\ \ \ \ \
| | | | | |
| | | | | | |
MAINT: Remove unnecessary backslashes (and replace others by using parenthesis)
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
See also: #13880
|
| |\ \ \ \ \ \
| | | | | | |
| | | | | | | |
MAINT: Replace integers in places where booleans are expected
|
| | |/ / / / / |
|
| |/ / / / /
| | | | |
| | | | |
| | | | |
| | | | | |
The methods max, min, ptp were missing the parameter
in the documentation.
|
| | | | | | |
|
| |\ \ \ \ \
| | | | | |
| | | | | | |
MAINT,BUG: Use nbytes to also catch empty descr during allocation
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
We do not want to allocate 0 bytes (since it is not well defined),
normally nbytes is 0 if the array is empty. But in case also the
descriptor element size is empty, use 1 byte.
|
| | | | | | | |
|
| |/ / / / / |
|
| |\ \ \ \ \
| | | | | |
| | | | | | |
DOC: Document the precise PCG variant.
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
Also, turn some of the reference URLs into links.
|
| | | | | | | |
|
| |/ / / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Nose is outdated and causes a DeprecationWarning during import,
a change in pytest seems to now trip over the warning, so ignore
it (in a slightly ugly manner)
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
When the base is not an array (or generally when the flag of the base
array was toggled), it is OK to allow setting the writeable flag to
True, as long as any ancestor (especially the last one) is writeable.
This commit also slightly change the behaviour of the base attribute.
---
* ENH: Deprecate writeable broadcast_array
* ENH: Make writeable flag enabling more reliable for non-array bases
When the base is not an array (or generally when the flag of the base
array was toggled), it is OK to allow setting the writeable flag to
True, as long as any ancestor (especially the last one) is writeable.
* Update doc/release/1.17.0-notes.rst
Co-Authored-By: Sebastian Berg <sebastian@sipsolutions.net>
* Update doc/release/1.17.0-notes.rst
Co-Authored-By: Sebastian Berg <sebastian@sipsolutions.net>
* Update numpy/lib/tests/test_stride_tricks.py
Co-Authored-By: Sebastian Berg <sebastian@sipsolutions.net>
* Update numpy/core/tests/test_multiarray.py
Co-Authored-By: Sebastian Berg <sebastian@sipsolutions.net>
* DOC: improve warning (from review)
|
| | | | | |
| | | | |
| | | | | |
* BUG: test, fix for big-endian systems
|
| |\ \ \ \ \
| | | | | |
| | | | | | |
BUG: Fix memory leaks in dtype constructor code
|
