summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorEric Wieser <wieser.eric@gmail.com>2017-12-23 11:47:26 +0000
committerEric Wieser <wieser.eric@gmail.com>2017-12-24 22:32:05 +0000
commitf0ffd58e7dbe8f4b111b0c090e8df0c3b779e1fe (patch)
treeb792cb73d4aa87560fbefb4bb8e442b0bba74e5c /doc
parentd45cf0b261b4a563f44fa238d34bd55f051f315f (diff)
downloadpython-numpy-f0ffd58e7dbe8f4b111b0c090e8df0c3b779e1fe.tar.gz
python-numpy-f0ffd58e7dbe8f4b111b0c090e8df0c3b779e1fe.tar.bz2
python-numpy-f0ffd58e7dbe8f4b111b0c090e8df0c3b779e1fe.zip
BUG: Allow nan values in the data when the bins are explicit
Fixes gh-7503 Closes gh-8984
Diffstat (limited to 'doc')
-rw-r--r--doc/release/1.15.0-notes.rst10
1 files changed, 10 insertions, 0 deletions
diff --git a/doc/release/1.15.0-notes.rst b/doc/release/1.15.0-notes.rst
index 60720deda..a24156ea0 100644
--- a/doc/release/1.15.0-notes.rst
+++ b/doc/release/1.15.0-notes.rst
@@ -64,6 +64,16 @@ to maintain compatibility, aliased at ``np.lib.function_base.histogram(dd)``.
Code that does ``from np.lib.function_base import *`` will need to be updated
with the new location, and should consider not using ``import *`` in future.
+``histogram`` will accept NaN values when explicit bins are given
+-----------------------------------------------------------------
+Previously it would fail when trying to compute a finite range for the data.
+Since the range is ignored anyway when the bins are given explcitly, this error
+was needless.
+
+Note that calling `histogram` on NaN values continues to raise the
+`RuntimeWarning`s typical of working with nan values, which can be silenced
+as usual with `errstate`.
+
``np.r_`` works with 0d arrays, and ``np.ma.mr_` works with ``np.ma.masked``
----------------------------------------------------------------------------
0d arrays passed to the `r_` and `mr_` concatenation helpers are now treated as