| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
there is a memset warning remaining when built with -flto, though its
not clear where exactly it comes from.
|
|
|
|
|
|
|
|
|
|
|
|
| |
Most of these fixes involve putting blank lines around
.. versionadded:: x.x.x
and
.. deprecated:: x.x.x
Some of the examples were also fixed.
|
| |
|
| |
|
|
|
|
|
|
|
| |
Rather than representing them as "-9223372036854775808",
we now represent them as "'NaT'", as in datetime64 arrays.
Note this changes the numpy.core.arrayprint printer, not the builtin
printer.
|
|\
| |
| | |
BUG: Make a @= b error out
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Before this change, we defined a nb_matrix_multiply slot but not a
nb_inplace_matrix_multiply slot, which means that a statement like
a @= b
would be silently expanded by the CPython interpreter to become
a = a @ b
This is undesireable, because it produces unexpected memory
allocations, breaks view relationships, and so forth.
This commit adds a nb_inplace_matrix_multiply slot which simply errors
out, and suggests that users write 'a = a @ b' explicitly if that's
what they want.
|
|\ \
| | |
| | | |
MANT: Cleanup of _pyarray_revert
|
| | |
| | |
| | |
| | |
| | | |
Removed several useless calls to copyswap, plus added a slightly
more efficient method for non-complex numeric types.
|
|\ \ \
| | | |
| | | | |
BUG: np.nonzero behaving differently for 1-D arrays
|
| | | |
| | | |
| | | |
| | | | |
Fixes #5837
|
|\ \ \ \
| | | | |
| | | | | |
BF: do not crash lookfor if inspection fails - catch any Exception
|
| | |/ /
| |/| | |
|
|\ \ \ \
| | | | |
| | | | | |
MAINT: core: less function pointer casting in arraytypes.c.src
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Filed upstream as:
https://github.com/nose-devs/nose/issues/929
Not our problem.
|
|\ \ \ \ \
| | | | | |
| | | | | | |
MAINT: remove legacy monkeypatching of GzipFile
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
I'm not sure exactly when GzipFile.seek started supporting the whence=
argument by default -- sometime around python 2.5 from the looks of
http://bugs.python.org/issue1355023. But in any case it was definitely
there by 2.6, which is now the earliest version we support, so there's
no longer any need to monkeypatch it in. This also fixes an error in
python 3.5b2, which I haven't bothered to track down further because
these are the wages of monkeypatching.
|
|/ / / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This triggers a PendingDeprecationWarning in py3.5 -- you're supposed
to just write "return" instead (which on earlier versions is
equivalent). See PEP 479: https://www.python.org/dev/peps/pep-0479/
|
| | | | | |
|
|\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
MAINT: fix two Wpedantic warnings in public header
Wpedantic is to strict to be really useful generally, but our public headers at least should avoid easy to avoid warnings for projects that do use this flag.
|
| | | | | | |
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
BUG: Added proper handling of median and percentile when nan's are prese...
|
| | | | | | | |
|
| | | | | | | |
|
| |/ / / / /
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
in array to close issue #586.
Also added unit tests.
|
|\ \ \ \ \ \
| |/ / / / /
|/| | | | | |
BUG: Fixed slicing of chararrays on Python 3.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
When taking a slice of a chararray it was calling the rstrip() method
on the resulting slice, resulting in a new array rather than a view
of the original. This was an unintended consequence of the sq_slice
member of the tp_as_sequence mapping being ignored in Python 3, so
that slice lookups go directly through __getitem__.
Fix test_expandtabs to not make the assumption that rstrip() will be applied twice to a value when using T[x][y] style indexing.
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
MAINT: Update version info for Numpy 1.10.
|
| | |_|_|_|/
| |/| | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Update version hash in numpy/core/code_generators/cversions.txt.
Update API version in numpy/core/setup_common.py
Update API version in numpy/core/include/numpy/numpyconfig.h
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
MAINT: eigenvalues returned by eigh are ascending
|
| | | | | | | |
|
| | | | | | | |
|
|/ / / / / / |
|
|/ / / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
In two places they were doing
>>> from StringIO import StringIO
Since Python 2.6 that should be
>>> from io import StringIO
Closes #5995.
|
|\ \ \ \ \
| | | | | |
| | | | | | |
DOC: Update indexing docs.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Update docs for boolean array indexing and nonzero order.
Add links to row-major and column-major terms where they appear.
Closes #3177
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
1.10 deprecated removal risky
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Risky perhaps. The old correlate behavior was deprecated in NumPy 1.4
and the default behavior changed to the new (standard) version in 1.5.
The old function, with slightly different signature, is still available
in numpy.core.multiarray.correlate.
If this causes problems in the 1.10 release process, this commit can be
reverted.
|
| |/ / / / /
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Deprecated in NumPy 1.5. If this causes problems in the 1.10 release
cycle the change can be reverted.
|
|/ / / / / |
|
|\ \ \ \ \
| | | | | |
| | | | | | |
1.10 deprecated removal
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Some keywords are deprecated and slated for removal in numpy 2.0.
Add comment to deprecation date to clarify that.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Deprecated, removed from numpy/core/arrayprint.py.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Deprecated functions in numpy/distutils/command/config.py.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Was in numpy/distutils/exec_command.py.
Update 1.10-notes.rst.
|
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This is to make it easier to find and remove deprecated features.
It would be a good idea if all deprecations were made with similar
comments.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This was deprecated in NumPy 1.7 with a warning that it would raise
an error in the future. Tests for the new error are added and the
test that allowed that special case is removed.
|