summaryrefslogtreecommitdiff
path: root/doc/release
Commit message (Collapse)AuthorAgeFilesLines
* Merge pull request #15997 from panpiort8/array_pretty_printMatti Picus2020-05-201-0/+12
|\ | | | | ENH: improve printing of arrays with multi-line reprs
| * Update doc/release/upcoming_changes/15997.improvement.rstpanpiort82020-05-201-4/+12
| | | | | | Co-authored-by: Eric Wieser <wieser.eric@gmail.com>
| * Improve the snippetPan Jan2020-05-201-3/+4
| |
| * Move the snippet notePan Jan2020-05-191-0/+3
| |
* | Merge pull request #16156 from WarrenWeckesser/deprecate-dualSebastian Berg2020-05-191-0/+5
|\ \ | | | | | | DEP: Deprecate `numpy.dual`.
| * | REL: Add a release note about the deprecation of numpy.dual.Warren Weckesser2020-05-051-0/+5
| | |
* | | REL: Update master after 1.19.x branch.Charles Harris2020-05-1740-315/+0
| | | | | | | | | | | | | | | | | | | | | | | | - Delete release note fragments from 1.19.0 (towncrier) - Update 1.19.x release note (towncrier) - Create 1.20.0-notes.rst for master development - Update C-API versions for 1.20.x - Update setup.py for 1.20.0
* | | Merge pull request #16269 from tbm/typoMatti Picus2020-05-171-1/+1
|\ \ \ | | | | | | | | DOC: Fix typos and cosmetic issues
| * | | DOC: Fix typos and cosmetic issuesMartin Michlmayr2020-05-171-1/+1
| | | |
* | | | BUG: numpy.einsum indexing arrays now accept numpy int type (gh-16080)Ryan2020-05-161-0/+4
|/ / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Using PyArray_PyIntAsIntp helper function instead * TST: add tests for einsum numpy int and bool list subscripts Added tests to check that einsum accepts numpy int64 types and rejects bool. Rejecting bools is new behaviour in subscript lists. I changed ValueError to TypeError on line 2496 in multiarraymodule.c as it is more appropriate. I also modified einsumfunc.py to have the same behaviour as in the C file when checking subscript list. (Reject bools but accept anything else from operator.index()) Closes gh-15961
* | | ENH: correct identity for logaddexp2 ufunc: -inf (gh-16102)Erik Welch2020-05-131-0/+4
| | | | | | | | | | | | | | | | | | | | | | | | The lack of identity for `logaddexp2` was first identitifed in #4599. The implementation in #8955 added -inf as identity for `logaddexp`, but missed adding it for `logaddexp2`. Co-Authored-By: Eric Wieser <wieser.eric@gmail.com> Co-authored-by: Sebastian Berg <sebastian@sipsolutions.net>
* | | DOC: Add release noteKevin Sheppard2020-05-121-0/+10
| | | | | | | | | | | | Add note detailing the changes to MT19937 jumped
* | | Merge pull request #16068 from seberg/string-to-bool-regressionCharles Harris2020-05-111-0/+11
|\ \ \ | | | | | | | | BUG: Fix string to bool cast regression
| * | | DOC: Release note for subtle C-API datetime cast fixSebastian Berg2020-05-111-0/+11
| | | |
* | | | ENH: Add equal_nan keyword argument to array_equal (gh-16128)Ross Barnowski2020-05-111-0/+6
| |/ / |/| | | | | | | | | | | | | | Match the corresponding kwarg and behavior from related functions like allclose. Co-authored-by: Sebastian Berg <sebastian@sipsolutions.net>
* | | Merge pull request #15769 from seberg/hugepages-allow-togglingMatti Picus2020-05-031-0/+15
|\ \ \ | | | | | | | | ENH: Allow toggling madvise hugepage and fix default
| * | | ENH: Allow toggling madvise hugepage and fix defaultSebastian Berg2020-03-171-0/+15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | By default this disables madvise hugepage on kernels before 4.6, since we expect that these typically see large performance regressions when using hugepages due to slow defragementation code presumably fixed by: https://github.com/torvalds/linux/commit/7cf91a98e607c2f935dbcc177d70011e95b8faff This adds support to set the behaviour at startup time through the ``NUMPY_MADVISE_HUGEPAGE`` environment variable. Fixes gh-15545
* | | | Merge pull request #16119 from seberg/misplaced-fragmentCharles Harris2020-05-011-0/+0
|\ \ \ \ | | | | | | | | | | DOC: Move misplaced news fragment for gh-13421
| * | | | DOC: Move misplaced news fragment for gh-13421Sebastian Berg2020-04-301-0/+0
| | |/ / | |/| |
* | | | ENH: update numpy.linalg.multi_dot to accept an `out` argument (#15715)sslivkoff2020-04-301-0/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * ENH: update numpy.linalg.multi_dot to accept an `out` argument * TST ensure value returned by numpy.linalg.multi_dot matches out * DOC add note about initial call to numpy.linalg.multi_dot * DOC add release note for #15715 Co-authored-by: Matti Picus <matti.picus@gmail.com> Co-authored-by: Sebastian Berg <sebastian@sipsolutions.net> Co-authored-by: Eric Wieser <wieser.eric@gmail.com>
* | | | BUG: Fix numpy.random.dirichlet returns NaN for small 'alpha' parameters. ↵Benjamin Trendelkamp-Schroer2020-04-291-0/+7
|/ / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | (#14924) * Add stick-breaking * Add tests demonstrating slowness for beta and dirichlet generators for small alpha (and beta) values * Remove the test for beta with small `a` and `b` * Switch from standard to stick-breaking method whenever alpha.max() < 0.1 Co-authored-by: Warren Weckesser <warren.weckesser@gmail.com> Co-authored-by: Eric Wieser <wieser.eric@gmail.com> Co-authored-by: Sebastian Berg <sebastian@sipsolutions.net>
* | | Merge pull request #15648 from xiegengxin/avx512-exp-float64Matti Picus2020-04-231-0/+7
|\ \ \ | |_|/ |/| | MAINT: AVX512 implementation with intrinsic for float64 input np.exp()
| * | MAINT: Fixed some spelling mistakes in 15648.improvement.rstGengxin Xie2020-04-081-3/+3
| | |
| * | DOC: Release note about upcoming changesGengxin Xie2020-04-071-0/+7
| | |
* | | BUG,DEP: Make `scalar.__round__()` behave like pythons round (#15840)Hameer Abbasi2020-04-102-0/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | See issue gh-15297 and related mailing list discussion. This PR bring scalar.__round__() in line with python, so that `round(scalar)` always returns a python integer, while `round(scalar, ndigits=0)` returns the same type. Since complex numbers are not supported in Python, and cannot be reasonably cast to integers they are deprecated. Closes gh-15297
* | | Merge pull request #15872 from Balandat/fix_eigh_mvn_samplingCharles Harris2020-04-041-0/+6
|\ \ \ | | | | | | | | BUG: Fix eigh and cholesky methods of numpy.random.multivariate_normal
| * | | Bug: Fix eigh mnd cholesky methods of numpy.random.multivariate_normalMax Balandat2020-04-041-0/+6
| | | | | | | | | | | | | | | | Fixes #15871
* | | | Merge pull request #15867 from eric-wieser/deprecate-tostringMatti Picus2020-04-011-0/+6
|\ \ \ \ | | | | | | | | | | DEP: Deprecate ndarray.tostring()
| * | | | Update doc/release/upcoming_changes/15867.deprecation.rstEric Wieser2020-04-011-2/+4
| | | | |
| * | | | DEP: Deprecate ndarray.tostring()Eric Wieser2020-03-301-0/+4
| | | | | | | | | | | | | | | | | | | | The corresponding `array.array.tostring()` in the standard library has been deprecated in favor of `tobytes` since Python 3.1 (python/cpython@1ce3eb5c5b4830e69b21865e2d723e22749544e0).
* | | | | ENH: Add keepdims argument to count_nonzero (gh-15870)Warren Weckesser2020-03-311-0/+5
| | | | | | | | | | | | | | | | | | | | Enables the keepdims argument (kwarg only) for count nonzero, since it is a reduce like operation.
* | | | | Merge pull request #15882 from ↵Matti Picus2020-03-311-0/+5
|\ \ \ \ \ | |_|/ / / |/| | | | | | | | | | | | | | eric-wieser/reject-illegal-strides-in-ndarray.__new__ BUG: Do not ignore empty tuple of strides in ndarray.__new__
| * | | | BUG: Do not ignore empty tuple of strides in ndarray.__new__Eric Wieser2020-03-311-0/+5
| |/ / / | | | | | | | | | | | | | | | | | | | | Previously this was treated as though an empty set of strides were passed. Now this is treated as a request for `.strides == ()`.
* | | | DEP: Do not cast boolean indices to integers in np.delete (#15815)Eric Wieser2020-03-251-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This expires a deprecation from 1.8. The corresponding deprecation in `np.insert` has less clear semantics, so has been left to a future patch. Co-authored-by: Sebastian Berg <sebastian@sipsolutions.net> Co-authored-by: Warren Weckesser <warren.weckesser@gmail.com>
* | | | Merge pull request #15802 from eric-wieser/simplify-insertEric Wieser2020-03-241-0/+9
|\ \ \ \ | |/ / / |/| | | DEP: Make `np.insert` and `np.delete` on 0d arrays with an axis an error
| * | | DEP: Make `np.insert` and `np.delete` on 0d arrays with an axis an errorEric Wieser2020-03-221-0/+9
| | |/ | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Before this change, the following code worked: ``` >>> some_0d = np.array(1) >>> np.insert(some_0d, "some nonsense", 10, axis=0) array(10) >>> np.insert(some_0d, "some nonsense", 42, axis="some nonsense") array(42) ``` Now these raise AxisError and TypeError, respectively. `delete` is exactly the same.
* | | Merge pull request #15804 from eric-wieser/expire-delete-out-of-boundsSebastian Berg2020-03-231-0/+8
|\ \ \ | | | | | | | | DEP: Make np.delete on out-of-bounds indices an error
| * | | DEP: Make np.delete on out-of-bounds indices an errorEric Wieser2020-03-221-0/+8
| |/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Note that this only affects lists of indices. ```python >>> a = np.arange(3) ```` Before: ```python >>> np.delete(a, 100) IndexError >>> np.delete(a, [100]) DeprecationWarning array([0, 1, 2]) >>> np.delete(a, -1) array([0, 1]) >>> np.delete(a, [-1]) FutureWarning array([0, 1, 2]) ``` After: ```python >>> np.delete(a, 100) IndexError >>> np.delete(a, [100]) IndexError >>> np.delete(a, -1) array([0, 1]) >>> np.delete(a, [-1]) array([0, 1]) ```
* | | Merge pull request #15805 from eric-wieser/expired-insert-delete-TypeErrorSebastian Berg2020-03-231-0/+6
|\ \ \ | | | | | | | | DEP: Forbid passing non-integral index arrays to `insert` and `delete`
| * | | DEP: Forbid passing non-integral index arrays to `insert` and `delete`Eric Wieser2020-03-221-0/+6
| |/ / | | | | | | | | | This expires a deprecation warning from back in 1.9.
* | | DEP: Make issubdtype consistent for types and dtypes (#15773)Sebastian Berg2020-03-221-0/+10
|/ / | | | | | | | | | | | | | | | | | | This finishes the deprecation started in gh-9505 removing behaviour that allowed strings/types representing specific dtypes to behave like their more generic supertypes (e.g. the python float would map to floating instead of float64 which it typically maps to). Co-Authored-By: Eric Wieser <wieser.eric@gmail.com>
* | BUG: add missing c_distributions.pxd, enables cython use of random C-API ↵Matti Picus2020-03-161-0/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | (gh-15463) xref gh-14778 As pointed out in the comment by @jamesthomasgriffin, we did not include a pxd file to expose the distribution functions documented in the random c-api. This PR adds a c_distributions.pxd file that exposes them. Squashed commits: * BUG: add missing c_distributions.pxd to enable cython use of random C-API * ENH, TST: add npyrandom library like npymath, test cython use of it * BUG: actually prefix f-string with f * MAINT: fixes from review, add _bit_generato_bit_generator.pxd * STY: fixes from review * BLD: don't use nprandom library for mtrand legacy build * TST: WindowsPath cannot be used in subprocess's list2cmdline * MAINT, API: move _bit_generator to bit_generator * DOC: add release note about moving bit_generator * DOC, MAINT: fixes from review * MAINT: redo dtype determination from review
* | ENH: Add `subok` parameter to np.copy function (cf. gfh6509) (gh-15685)Ross Barnowski2020-03-111-0/+9
| | | | | | | | | | This is largely a re-submission of the original change proposed in #6509. Discussion was hosted in multiple forums including #3474, the numpy mailing list circa 10-2015, and the 02-26-2020 NumPy Triage meeting. This PR closes #3474 and #15570
* | Merge pull request #15534 from seberg/deprecate-abstract-scalar-typesMatti Picus2020-03-061-0/+11
|\ \ | | | | | | DEP: Do not allow "abstract" dtype conversion/creation
| * | DEP: Do not allow "abstract" dtype conversion/creationSebastian Berg2020-02-061-0/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | These dtypes do not really make sense as instances. We can (somewhat) reasonably define np.dtype(np.int64) as the default (machine endianess) int64. (Arguably, it is unclear that `np.array(arr_of_>f8, dtype="f")` should return arr_of_<f8, but that would be very noisy!) However, `np.integer` as equivalent to long, is not well defined. Similarly, `dtype=Decimal` may be neat to spell `dtype=object` when you intend to put Decimal objects into the array. But it is misleading, since there is no special meaning to it at this time. The biggest issue with it, is that `arr.astype(np.floating)` looks like it will let float32 or float128 pass, but it will force a float64 output! Arguably downcasting is a bug in this case. A related issue is `np.dtype("S")` and especially "S0". The dtype "S" does make sense for most or all places where `dtype=...` can be passed. However, it is conceptionally different from other dtypes, since it will not end up being attached to the array (unlike "S2" which would be). The dtype "S" really means the type number/DType class of String, and not a specific dtype instance.
* | | Merge pull request #14995 from seberg/array-like-coercionMatti Picus2020-02-261-0/+10
|\ \ \ | |_|/ |/| | BUG: Use ``__array__`` during dimension discovery
| * | BUG: Use ``__array__`` during dimension discoverySebastian Berg2020-02-051-0/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | ``__array__`` was previously not used during dimension discovery, while bein gused during dtype discovery (if dtype is not given), as well as during filling of the resulting array. This would lead to inconsistencies with respect to array likes that have a shape including a 0 (typically as first dimension). Thus a shape of ``(0, 1, 1)`` would be found as ``(0,)`` because a nested list/sequence cannot represent empty shapes, except 1-D. This uses the `_array_from_array_like` function, which means that some coercions may be tiny bit slower, at the gain of removing a lot of complex code. (this also reverts commit d0d250a3c9d7d90e75701c32d7d435640e6b02eb or the related change). This is a continuation of work by Sergei Lebedev in gh-13663 which had to be reverted due to problems with Pandas, and the general inconsistency. This version may not resolve all issues with pandas, but does resolve the inconsistency. Closes gh-13958
* | | ENH: Implement the buffer protocol on numpy str_ scalarsEric Wieser2020-02-081-0/+5
| |/ |/| | | | | This eliminates the need for special casing in `np.generic.__reduce__`
* | Merge pull request #13421 from seiko2plus/core_improve_infa_runtimeMatti Picus2020-02-051-0/+8
|\ \ | |/ |/| ENH: improve runtime detection of CPU features
| * DOC: add a release notemattip2020-02-052-0/+9
| |
View Lorry Controller Status