diff options
| author | mattip <matti.picus@gmail.com> | 2018-10-26 13:46:35 +0300 |
|---|---|---|
| committer | mattip <matti.picus@gmail.com> | 2018-10-26 13:49:32 +0300 |
| commit | b8d9543513ee85c8f7af10edf462afd753a166da (patch) | |
| tree | 7698762c67c887d0b78abde57129fe9d4026e695 | |
| parent | 24c9faac737321933022104843a435ccb329cc0b (diff) | |
| download | numpy-b8d9543513ee85c8f7af10edf462afd753a166da.tar.gz | |
DOC: revise release note
| -rw-r--r-- | doc/release/1.16.0-notes.rst | 13 |
1 files changed, 7 insertions, 6 deletions
diff --git a/doc/release/1.16.0-notes.rst b/doc/release/1.16.0-notes.rst index 599123f97..4491deb34 100644 --- a/doc/release/1.16.0-notes.rst +++ b/doc/release/1.16.0-notes.rst @@ -266,12 +266,13 @@ if ``np.positive(array)`` raises a ``TypeError``. For ``ndarray`` subclasses that override the default ``__array_ufunc__`` implementation, the ``TypeError`` is passed on. -``maximum`` and ``minimum`` set invalid float status for more dtypes --------------------------------------------------------------------- -Previously only ``float32`` and ``float64`` set invalid float status (by -default emitting a `RuntimeWarning`) when a Nan is encountered in -`numpy.maximum` and `numpy.minimum`. Now ``float16``, ``complex64``, -``complex128`` and ``complex256`` will do so as well. +``maximum`` and ``minimum`` no longer emit warnings +--------------------------------------------------- +As part of code introduced in 1.10, ``float32`` and ``float64`` set invalid +float status when a Nan is encountered in `numpy.maximum` and `numpy.minimum`, +when using SSE2 semantics. This caused a `RuntimeWarning` to sometimes be +emitted. In 1.15 we fixed the inconsistencies which caused the warnings to +become more conspicuous. Now no warnings will be emitted. Umath and multiarray c-extension modules merged into a single module -------------------------------------------------------------------- |