| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
Subclass input of piecewise was already respected, so it seems more
logical to ensure the output is the same subclass (possibly just an
oversight that it was not done before).
|
|
|
|
| |
being returned
|
|
|
|
|
|
|
|
|
|
|
|
| |
... or when the input isn't/cannot be a set. I left a few usages, e.g.
in random sampling, where "set" is reasonable as informal description of
an array as the order doesn't matter; however, for e.g. np.gradient the
order of the returned list is clearly important, so "set" is wrong.
Also some other minor doc edits noticed during the grepping: using
`shape` instead of `form` in `cov` is consistent with most other places;
the wording in `Polynomial.trim` now matches other methods on the same
class.
|
| |
|
|
|
|
|
|
|
| |
Adds a keyword-only dtype parameter to correlate and coerrcoef to allow
user to specify the dtype of the output.
Co-authored-by: Eric Wieser <wieser.eric@gmail.com>
Co-authored-by: Ross Barnowski <rossbar@berkeley.edu>
|
|
|
| |
* DOC: Fix typos in versionchanged.
|
| |
|
| |
|
|
|
|
|
|
| |
This relies on the fact that `cos` is exactly symmetric around zero, but not around the floating-point approximation of `pi`.
Closes gh-17169.
|
| |
|
|
|
|
| |
Fix spacing that produced incorrect rendering
|
|\
| |
| | |
MAINT: Revert boolean casting back to elementwise comparisons in `trim_zeros`
|
| | |
|
| | |
|
| | |
|
|/
|
|
| |
* BUG, API: Raise error on complex input to np.i0
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Added a benchmark for `trim_zeros()`
* Improve the performance of `np.trim_zeros()`
* Increase the variety of the tests
Fall back to the old `np.trim_zeros()` implementation if an exception is encountered.
Emit a `DeprecationWarning` in such case.
* DEP,REL: Added a deprecation release note
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
ENH: added edge keyword argument to digitize
added test
|
|
|
|
|
|
|
| |
(#16811)
* DOC: update parameter choices for asarray, asarray_contiguous, asarray_chkfinite converters
Co-authored-by: sun <sun@vosdbt.org>
|
| |
|
|\
| |
| | |
BUG: Order percentile monotonically
|
| |
| |
| | |
Co-authored-by: Eric Wieser <wieser.eric@gmail.com>
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* 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
|
|\
| |
| |
| |
| | |
LSchroefl/link_SciPy_multidimensional_interpolation
DOC: link np.interp to SciPy's interpolation functions (closes #14154)
|
| |
| |
| | |
Co-authored-by: Ross Barnowski <rossbar@berkeley.edu>
|
| | |
|
|\ \
| | |
| | | |
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.
|
| |
| |
| |
| | |
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
|