| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Replace "matrix" with "array" to avoid confusion
re: np.matrix. Consistent with other np.tri\* functions.
|
| |
|
| |
|
|
|
|
|
|
| |
In loadtxt, there is a try/finally block that ensures that the file
is closed if it was opened in the function. Some code that did not
need to be in that block was moved up, outside the try/finally block.
|
|
|
|
|
|
| |
Validation of `ndmin` is moved to the beginning of the function,
so we don't read the entire file only to raise an exception at
the end because of a bad argument.
|
|
|
|
|
| |
This change moves the nested function definitions in loadtxt
to the top of the function body.
|
|
|
|
| |
This is a follow up to d1d9dd58e2de5f3b69c02b104e1daaeec1f38d9f, as more regressions in this style have been introduced since that commit.
|
|\
| |
| | |
DOC: Point Contributing page to new NEP 45
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Per #16500 discussion, adds link updates to PR.
Replaces NEP URLs with intersphinx links in these
files:
* doc/HOWTO_RELEASE.rst.txt
* doc/source/dev/howto-docs.rst
* numpy/doc/dispatch.py
* numpy/lib/format.py
and incorporates @rossbar's #16502 change of `config.py`.
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* DOC: Fixes for 18 broken links
This, with PR #16465, should fix nearly all the remaining broken links
on the site. 4 or 5 others should be easy to fix and just
need attention from someone more knowledgeable -- will
open an issue. For release notes with dead links,
I could usually find links on archive.org for roughly contemporary
versions.
* DOC: Update to "Fixes for 18 broken links #16472"
* Obsolete links, previously commented out, now deleted:
https://github.com/numpy/numpy/pull/16472#discussion_r433928958
* Semantic markup for reference to Python class:
https://github.com/numpy/numpy/pull/16472#discussion_r433553928
* Missing :ref: in internal link:
https://github.com/numpy/numpy/pull/16472#discussion_r433554484
Not included: Resolution on using external/internal doc link in .py:
https://github.com/numpy/numpy/pull/16472#discussion_r433554824
* DOC: Add internal link for 'Fixes for 18 broken links' PR #16472
Making reference [1] an internal link in function_base.py => numpy.vectorize.html
* DOC: Redirect 2 link fixes in PR #16472
* governance.rst link reverted
* ununcs.rst `overridden` link goes where it was meant to
per https://github.com/numpy/numpy/pull/16472#pullrequestreview-424666070
|
|
|
|
| |
Minor cleanup while looking at something else.
|
|
|
|
| |
Addresses gh-13457
|
| |
|
|\
| |
| | |
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.
|
|\ \
| | |
| | |
| | |
| | | |
LSchroefl/link_SciPy_multidimensional_interpolation
DOC: link np.interp to SciPy's interpolation functions (closes #14154)
|
| | |
| | |
| | | |
Co-authored-by: Ross Barnowski <rossbar@berkeley.edu>
|
| |/ |
|
|\ \
| | |
| | | |
BUG,DOC: Allow attach docs twice but error if wrong
|
| | |
| | |
| | |
| | |
| | | |
Its not quite the right file, but close to newdoc seemed sensible
and we do not have a "right" file right now...
|
|\ \ \
| |/ /
|/| | |
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
|
|\ \
| | |
| | | |
DEP: Deprecate `numpy.dual`.
|
| | |
| | |
| | |
| | |
| | |
| | | |
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
|
| | |
| | |
| | |
| | | |
It's easier to move the relevant axis to position 0 in `ap` first than it is to move it for every relevant object simultaneously.
|
| | |
| | |
| | |
| | | |
The `add` ufunc is happy to handle `out=None` by itself
|
| | | |
|
|\ \ \
| |/ /
|/| | |
DOC: Unify cross-references between array joining methods
|
| | | |
|
|\ \ \
| |/ /
|/| | |
MAINT: cleanups to _iotools.StringConverter
|
| | |
| | |
| | |
| | | |
The previous logic here was very hard to follow, as loop variables were being used after the loop ended, and being conditionally overwritten.
|
| | | |
|
| | | |
|
| |/
| |
| |
| | |
Also fix the docstring indentation
|
| |
| |
| |
| |
| |
| |
| |
| | |
(#16129)
* Improved one of the error messages for histogramdd.py as outlined in issue #15984
Co-authored-by: Eric Wieser <wieser.eric@gmail.com>
|
| | |
|
|\ \
| | |
| | | |
BUG: lib: Fix a problem with vectorize with default parameters.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Added a note to some of the tests that the order of the calls is an
important part of the test, because the code is testing the caching
of the ufuncs.
Also reuse a couple functions in the vectorize tests by defining them at
the module level.
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When `otypes` is given to `vectorize` and then the instance is
called, it creates a ufunc by calling numpy.core.umath.frompyfunc.
The number of arguments given to this ufunc is set to the number
of arguments in the call of the vectorize instance. This ufunc
is cached, so frompyfunc does not have to be called on the next
call. The problem is that, if the function being wrapped has
parameters with default values, the number of arguments passed
to the vectorize instance can change, and when that happens, a
new ufunc must be created by calling frompyfunc with the correct
number of arguments.
This commit changes the cache of the ufunc from a simple attribute
that holds the most recent ufunc to a dictionary whose keys are
the number of arguments in the call. The cache is only used when
the vectorized function is called with only positional arguments
and there are no excluded arguments. If keywords are used, the
number of arguments is no longer sufficient to uniquely identify a
previously created ufunc.
Closes gh-16120.
|
|/
|
|
|
|
|
|
|
| |
We only do a shallow copy of arrays (mainly important for object arrays), so
mention that in the documentation.
Fixes #15923
Co-Authored-By: Eric Wieser <wieser.eric@gmail.com>
Co-Authored-By: Ross Barnowski <rossbar@berkeley.edu>
|
|\
| |
| | |
ENH: Fix exception causes in four .py files
|