| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
[skip actions] [skip travis] [skip cirrus]
|
|
|
|
| |
[skip actions] [skip travis] [skip azp] [skip cirrus]
|
|
|
|
| |
[skip actions] [skip travis] [skip azp] [skip cirrus]
|
| |
|
| |
|
|\
| |
| | |
MAINT: Ensure graceful handling of large header sizes
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This ensures graceful handling of large header files. Unfortunately,
it may be a bit inconvenient for users, thus the new kwarg and the
work-around of also accepting allow-pickle.
See also the documation here:
https://docs.python.org/3.10/library/ast.html#ast.literal_eval
|
|/
|
|
|
|
|
|
|
|
|
| |
Some BaseExceptions (at least the Skipped that pytest uses) need to
be caught as well. It seems easiest to be practical and keep ignoring
almost all exception in this particular code path.
Effectively reverts parts of gh-19393
Closes gh-22345
Co-authored-by: Sebastian Berg <sebastianb@nvidia.com>
|
| |
|
|
|
|
|
|
| |
Currently the location of the function definition is always reported
to be `numpy.lib.utils`; this changes it to be the location of the
actual definition when possible.
|
| |
|
|
|
|
|
|
|
|
| |
1. Information is derived with the help of `threadpoolctl` library.
2. In case `threadpoolctl` is not installed, a message is displayed
with help on how to install it.
3. SIMD related information is derived from `__cpu_features__`,
`__cpu_baseline__` and `__cpu_dispatch__`
|
|
|
|
|
|
|
|
|
| |
Having the `::` on new line can be ambiguous for RST parsers,
as `:` is a valid character for header underlines. And as underlines do
not have to be as long as the title for some rst parser this appears to
be a title.
Workaround is to have either a blank line, or put the `::` at the end of
previous one.
|
| |
|
| |
|
|
|
|
| |
in Google Colab. Closes#20423
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
Currently, np.median is almost completely safe for subclasses, except
if the result is NaN. In that case, it assumes the result is a scalar
and substitutes a NaN with the right dtype. This PR fixes that, since
subclasses like astropy's Quantity generally use array scalars to
preserve subclass information such as the unit.
|
| |
|
|
|
| |
Co-authored-by: Matti Picus <matti.picus@gmail.com>
|
|
|
|
| |
Relates to ticket #19077
|
|
|
|
| |
of NumPy build
|
|
|
|
| |
Otherwise Numpydoc does not see the section.
|
|\
| |
| | |
DOC: Fix docstring of _median_nancheck.
|
| |
| |
| |
| |
| |
| | |
_median_nancheck doesn't support axis being anything other than an
integer (otherwise the call to moveaxis would fail). This is fine,
because median goes through _ureduce for multi-axis support.
|
|/
|
|
|
|
| |
This change speeds up taking the median of 1001 floats by ~20%, as
measured by
`python -mtimeit -s 'import numpy as np; x = np.random.randn(1001)' -- 'np.median(x)'`
|
|
|
|
|
|
| |
* Add doc for deprecate_with_doc
Co-authored-by: Bas van Beek <43369155+BvB93@users.noreply.github.com>
Co-authored-by: Matti Picus <matti.picus@gmail.com>
|
|
|
|
|
| |
Fixes the incompatible type comparison found in #17490.
This also corrects the logic to not print the heading when only private/magic methods are present.
|
|\
| |
| | |
BUG: Indentation for docstrings
|
| | |
|
|/
|
|
|
|
| |
Using inspect.signature instead of `np.compat.getargspec` solves this problem.
`inspect.signature` also handles stripping the `self` argument of methods for us.
|
|
|
|
|
|
|
| |
`global` is only needed if a variable appears on the left of an assignment.
These variables do not.
Most suffer from the misconception that `var[x] = y` requires `var` to be global, but it does not.
|
|
|
| |
More sys.version cleanup.
|
| |
|
|
|
|
|
|
|
| |
Inheriting from object was necessary for Python 2 compatibility to use
new-style classes. In Python 3, this is unnecessary as there are no
old-style classes.
Dropping the object is more idiomatic Python.
|
|
|
|
|
| |
As numpy is Python 3 only, these import statements are now unnecessary
and don't alter runtime behavior.
|
| |
|
|
|
|
| |
* Deprecate class SafeEval
|
| |
|
| |
|
| |
|
|
|
|
| |
Closes #8058.
|
| |
|
|
|
|
|
|
|
|
|
| |
* added lib.recfunctions to refguide
PUBLIC_SUBMODULES, as the doctests
were otherwise not getting executed
* fixed a failing doctest in
recfunctions after above activation
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* restored regression comment in
numpy/core/defchararray.py
* fixed the dimensionality of the z
array in all() docstring in
numpy/core/fromnumeric.py; this isn't
detected because it is in-line with
variable memory addresses which are
tagged as variable for refguide
* byte_bounds() docstring adjusted
to reflect non-variable dtype
after reviewer requested removal
of complex dtype
* restore an original comment
in matmul docstring, as requested
by reviewer
|
| |
|
|
|
|
|
|
|
|
| |
* ported the refguide_check module from SciPy for usage
in NumPy docstring execution/ verification; added the
refguide_check run to Azure Mac OS CI
* adjusted NumPy docstrings such that refguide_check passes
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fixes GH-12271
Tests verify that everything in ``dir(numpy)`` either has ``__module__`` set to
``'numpy'``, or appears in an explicit whitelist of undocumented functions and
exported bulitins. These should eventually be documented or removed.
I also identified a handful of functions for which I had accidentally not setup
dispatch for with ``__array_function__`` before, because they were listed under
"ndarray methods" in ``_add_newdocs.py``. I guess that should be a lesson in
trusting code comments :).
|