summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRalf Gommers <ralf.gommers@gmail.com>2018-07-22 10:23:52 -0700
committerRalf Gommers <ralf.gommers@gmail.com>2018-07-22 10:24:39 -0700
commit5ee09d47c7212b2f029408b0197e6954421dca38 (patch)
tree08cf63229806172a760a571a4905b70a7730b6ba
parent38b567053977f80a36209cd7357521b6b4049d84 (diff)
downloadnumpy-5ee09d47c7212b2f029408b0197e6954421dca38.tar.gz
MAINT: address review comment of @shoyer, remove reference to ``legacy_index``.
[ci skip]
-rw-r--r--doc/neps/nep-0023-backwards-compatibility.rst8
1 files changed, 3 insertions, 5 deletions
diff --git a/doc/neps/nep-0023-backwards-compatibility.rst b/doc/neps/nep-0023-backwards-compatibility.rst
index da4044feb..158b08f1f 100644
--- a/doc/neps/nep-0023-backwards-compatibility.rst
+++ b/doc/neps/nep-0023-backwards-compatibility.rst
@@ -82,11 +82,9 @@ A new keyword ``density`` was introduced to replace it; ``normed`` started givin
# v1.15.0 was the first release where `normed` started emitting
# DeprecationWarnings
-The ``new`` keyword was planned from the start to be temporary; such a plan
-forces users to change their code more than once. Such keywords (there have
-been other instances proposed, e.g. ``legacy_index`` in
-`NEP 21 <http://www.numpy.org/neps/nep-0021-advanced-indexing.html>`_) are not
-desired. The right thing to have done here would probably have been to
+The ``new`` keyword was planned from the start to be temporary. Such a plan
+forces users to change their code more than once, which is almost never the
+right thing to do. Instead, a better approach here would have been to
deprecate ``histogram`` and introduce a new function ``hist`` in its place.
**Returning a view rather than a copy**