| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
[ci-skip]
|
| |\
| |
| | |
DOC: add versionadded for NDArrayOperatorsMixin.
|
| |/ |
|
| |
|
|
|
|
|
|
| |
* [BUG] add "symmetric" to "positive-semidefinite"
* Break line, fix comments
* break long line
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* BUG: improve parsing of quoted control characters in numpy.f2py.
See #10634. Fixes a couple of cases where quoted control
characters are parsed as if they are unquoted. The control
characters considered are "()!;".
* TST: quoted characters parsing by numpy.f2py.
Basic test of parsing quoted Fortran control characters. See #10634.
* BUG: add missing space character when reconstructing fortran line.
The missing space caused a line starting with "!f2py" to be considered
a continuation line.
|
| |\
| |
| | |
DOC zeros, empty, and ones now have consistent docstrings
|
| | |
| |
| |
| | |
closes #10611
|
| |\ \
| | |
| | | |
DOC: Fix incorrect formula in gradient docstring.
|
| | | | |
|
| |\ \ \
| |_|/
|/| | |
DOC: Add installation notes for Linux users
|
| | | |
| | |
| | | |
[skip ci]
|
| | | | |
|
| | | | |
|
| | | | |
|
| |\ \ \
| | | |
| | | | |
ENH: Implement axes keyword argument for gufuncs.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This ensures we do not have to guard against any operand having
fewer dimensions than required by the ufunc in, e.g.,
_parse_axes_argument.
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The axes argument allows one to specify the axes on which
the gufunc will operate (by default, the trailing ones).
It has to be a list with length equal to the number of
operands, and each element a tuple of length equal to the
number of core dimensions, with each element an axis index.
If there is only one core dimension, the tuple can be
replaced by a single index, and if none of the outputs have
core dimensions, the corresponding empty tuples can be
omitted.
|
| |\ \ \ \
| |/ / /
|/| | | |
STY: Minor stylistic cleanup of numeric.py
|
| |/ / /
| | |
| | |
| | | |
No changes to the logic, only minor edits guided by flake8.
|
| |\ \ \
| | | |
| | | | |
DOC/MAINT: More misc. typos
|
| | | | |
| | | |
| | | | |
Found via `codespell` and `grep`
|
| |\ \ \ \
| |/ / /
|/| | | |
MAINT: Unify reductions in fromnumeric.py
|
| |/ / / |
|
| |\ \ \
| | | |
| | | | |
BUG: Make np.partition and np.sort work on np.matrix when axis=None
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Both were making the normally valid assumption that flatten actually flattens, which turns out to be false for matrices.
Old behavior:
>>> a = np.matrix([[1, 2, 0]])
>>> np.partition(a, 1, axis=None)
ValueError: kth(=1) out of bounds (1)
>>> np.sort(a, axis=None)
matrix([[1, 2, 0]])
|
| |\ \ \ \
| | | | |
| | | | | |
BUG/MAINT: Remove special cases for 0d arrays in interp
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
These are now handled generically by the underlying C function
This fixes the period argument for 0d arrays.
Now never returns a pure-python scalar, which matches the behaviour of most of numpy.
Rework of b66a200a4a1e98f1955c8a774e4ebfb4588dab5b
|
| | |/ / /
| | | |
| | | |
| | | |
| | | |
| | | | |
Like other functions, returns a numpy scalar in place of 0d arrays
Previously this would throw an exception
|
| |\ \ \ \
| |/ / /
|/| | | |
MAINT: Remove duplicate implementation for aliased functions.
|
| | | | |
| | | |
| | | |
| | | | |
Fixes #10651 by replacing the behavior of `product` with that of `prod`
|
| |\ \ \ \
| | | | |
| | | | | |
BUG: f2py: fix f2py generated code to work on Pypy
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
F2py generates code that uses PyTuple_SetItem on a tuple that has been
"used", which is invalid on Pypy.
Add #ifdefs that make the generated code convert the object to a list,
use PyList_SetItem, and then convert it back to a tuple.
|
| |\ \ \ \ \
| |/ / / /
|/| | | | |
BUG: Fix missing NPY_VISIBILITY_HIDDEN on npy_longdouble_to_PyLong
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Fixes #10648
NPY_VISIBILITY_HIDDEN is used by memoverlap.{c,h}, so we should be using the same thing here
|
| |\ \ \ \ \
| | | | | |
| | | | | | |
MAINT: Post 1.14.1 release updates for master branch
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
[ci skip]
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
[ci skip]
|
| |\ \ \ \ \ \
| |/ / / / /
|/| | | | | |
ENH: Make flatnonzero call asanyarray before ravel()
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
It now works for lists and other numpy-convertible input.
Fixes #10598.
|
| | | | | | | |
|
| |\ \ \ \ \ \
| | | | | | |
| | | | | | | |
[BUG] Improving the accuracy of the FFT implementation
|
| |/ / / / / /
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Previously, the numerical constants in the FFT code were not provided at full double precision which led to a loss of accuracy in the FFT operation. Additionally
this commit improves the accuracy of the twiddle factor calculation by reducing the argument of exp(2j*pi*m/n) to the first octant before calling the library
function. On average the commit lowers the remaining numerical error in the FFT by a factor of ten.
|
| |\ \ \ \ \ \
| | | | | | |
| | | | | | | |
BUG: fromregex: asbytes called on regexp objects
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
When calling fromregex() with a binary stream and a regular expression
object, asbytes() was called on the regexp object, resulting in an
incorrect regular expression being compiled and used.
|
| |\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
BUG: deallocate recursive closure in arrayprint.py
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Fixes #10620
|
| |\ \ \ \ \ \ \ \
| |/ / / / / / /
|/| | | | | | | |
BUG: Correctly identify comma seperated dtype strings
|
| |/ / / / / / /
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
When parsing dtype strings, we should only consider them to
be comma seperated if there are commas not present in a
pair of square brackets.
Whilst we had a check for this already in the code there was
an off by 1 bug where we failed to consider the first character
of the string. This would lead to an infinite recursion when
trying to parse strings of the form `[i8,f8]`.
Fixes: #10440
|
| |\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
DOC: promote_types is _not_ associative by design,
|
