| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| | |
ENH: include dt64/td64 structs and funcs and tests in __init__.pxd.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
|\ \
| | |
| | | |
BUG: Fix dtype leak in `PyArray_FromAny` error path
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Also adds a test to bincount which will run into this path.
The leak can be triggered by using a reference count checker
on the test suit (e.g. pytest-leaks).
Closes gh-16339
|
|\ \ \
| | | |
| | | | |
BUG: Indentation for docstrings
|
| | | | |
|
|\ \ \ \
| |/ / /
|/| | | |
BUG: np.info does not show keyword-only arguments
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Using inspect.signature instead of `np.compat.getargspec` solves this problem.
`inspect.signature` also handles stripping the `self` argument of methods for us.
|
| |/ /
|/| |
| | |
| | |
| | |
| | |
| | | |
Remove support for Apple Accelerate, since it is buggy. A build error should
occur on most or all setups if linked against Accelerate. Test or import failures
should occur on setups where Accelerate is picked up dynamically.
Co-authored-by: Warren Weckesser <warren.weckesser@gmail.com>
|
|\ \ \
| | | |
| | | | |
BUG: Fix refcounting in add_newdoc
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
this is a trivial refcounting fix, since this function is mostly
used only at startup, the small refcounting issue was not noticed
until the new tests were added.
|
|\ \ \ \
| | | | |
| | | | | |
DOC: Fix spelling typo - homogenous to homogeneous. (#16324)
|
| | | | | |
|
|\ \ \ \ \
| |_|_|_|/
|/| | | |
| | | | |
| | | | | |
LSchroefl/link_SciPy_multidimensional_interpolation
DOC: link np.interp to SciPy's interpolation functions (closes #14154)
|
| | | | |
| | | | |
| | | | | |
Co-authored-by: Ross Barnowski <rossbar@berkeley.edu>
|
| | |_|/
| |/| | |
|
| |/ /
|/| |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
When __getitem__ fails, assignment falls back on __iter__, which may not
have the same length as __len__, resulting in a segfault.
See gh-7264.
* BUG: Don't rely on __len__ for safe iteration.
Skip __len__ checking entirely, since this has no guarantees of being
correct. Instead, first convert to PySequence_Fast and use that length.
Also fixes a refleak when creating a tmp array fails.
See gh-7264.
* TST: Update test for related edge-case.
The previous fix more gracefully handles this edge case by skipping the
__len__ check. Rather than raising with an unhelpful error message, just
create the array with whatever elements C() actually yields.
See gh-7264.
|
| |/
|/|
| |
| |
| | |
Python 3.9 started to deprecate these calls and the PyObject_Call*
variants are equivalent or nicer in any case.
|
|\ \
| | |
| | | |
ENH: improve printing of arrays with multi-line reprs
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
|\ \ \
| | | |
| | | | |
BUG,DOC: Allow attach docs twice but error if wrong
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The old pointers are now provided by the C-API and the macros
seemed a bit confusing since ``new`` appears from nowhere being
defined in the macro.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Its not quite the right file, but close to newdoc seemed sensible
and we do not have a "right" file right now...
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Previously some of these were not set, because they were already
set on the C-level. Remove the duplicate message and replace it
instead with a forward to the ``ndarray`` attribute/method.
These docstrings are inherited by the actual scalars and thus the
"virtual class" note was misleading.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This is technically not a bug, but some IDEs and IPython have
autoreload magic which can mean that NumPy gets reloaded a second
time. This is not safe, but when it happens ignoring that an
identical docstring is already attached fixes the issue.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
I found that when building the latest master branch on Cygwin, while testing #16246, that thousands of warnings were generated at build time like:
numpy/core/src/npysort/binsearch.c.src: In function ‘binsearch_left_bool’:
numpy/core/src/npysort/binsearch.c.src:82:1: warning: visibility attribute not supported in this configuration; ignored [-Wattributes]
Granted this is just a warning, so I don't think it's a serious issue.
It seems the test that was supposed to check for __attribute__ support was not working as expected. The #pragmas only take effect if I provide a function body--they are ignored for bare declarations. I don't know if that's by intent, or if it's a GCC issue. For reference:
$ gcc --version
gcc (GCC) 7.4.0
|
| | | |
| | | |
| | | |
| | | |
| | | | |
* BUG: relpath fails for different drives on windows
* ENH: always use abspath
|
|\ \ \ \
| | | | |
| | | | | |
MAINT: Clean up the implementation of quantile
|
| | | | |
| | | | |
| | | | | |
take now correctly returns `out`, even on 0d arrays
|
| | | | |
| | | | |
| | | | |
| | | | | |
This also simplifies the axis handling logic, taking advantage of the fact we know `axis` is 0 for the rest of the function body
|
| | | | |
| | | | |
| | | | |
| | | | | |
This does not affect the behavior in any way
|
| |/ / /
|/| | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
the => seem to be extra and rst seem to not interprete backtick with
leading space as closing a directive, the the full line on text was put
in a html pre-tag when building the docs.
see current https://numpy.org/doc/stable/reference/generated/numpy.packbits.html
|
| | | |
| | | |
| | | |
| | | | |
Most compilers should optimize it, but it doesn't hurt to inline and has a better name
now.
|
|\ \ \ \
| | | | |
| | | | | |
DEP: Deprecate `numpy.dual`.
|
| | | | |
| | | | |
| | | | |
| | | | | |
Also make the correction "Scipy" -> "SciPy" in a few places.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Add a deprecation warning in the `numpy.dual` module, and
remove the use of `numpy.dual` from the few places where it
is used in the numpy code.
|
|\ \ \ \ \
| | | | | |
| | | | | | |
BUG: Fix default fallback in genfromtxt
|
| | | | | |
| | | | | |
| | | | | | |
Co-authored-by: Eric Wieser <wieser.eric@gmail.com>
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This affected (for example?) if the `dtype=object` was used
without a converter, meaning that the default one is used.
And this is currently the last one, which is `string_` (and thus
bytes).
Closes gh-16189
|