summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorSebastian Berg <sebastian@sipsolutions.net>2021-01-26 12:24:36 -0600
committerGitHub <noreply@github.com>2021-01-26 12:24:36 -0600
commit4eb79d8cb0ffabd64f1aae727ecd1a7b749501d3 (patch)
tree4821fcd560d92d28b3f0f65c84323de5092ff85e /doc
parent4a28dff89766b30dfa82f41f45ea03fdc70accd4 (diff)
downloadnumpy-4eb79d8cb0ffabd64f1aae727ecd1a7b749501d3.tar.gz
Update doc/source/release/1.20.0-notes.rst
Co-authored-by: Eric Wieser <wieser.eric@gmail.com>
Diffstat (limited to 'doc')
-rw-r--r--doc/source/release/1.20.0-notes.rst4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/source/release/1.20.0-notes.rst b/doc/source/release/1.20.0-notes.rst
index d191e9ee1..aab5b34a9 100644
--- a/doc/source/release/1.20.0-notes.rst
+++ b/doc/source/release/1.20.0-notes.rst
@@ -106,7 +106,8 @@ For ``float`` and ``complex`` you can use ``float64`` and ``complex128``
if you wish to be more explicit about the precision.
For ``np.int`` a direct replacement with ``np.int_`` or ``int`` is also
-good, but the precision depends on the computer and operating system.
+good and will not change behavior, but the precision will continue to depend
+on the computer and operating system.
If you want to be more explicit and review the current use, you have the
following alternatives:
@@ -1000,4 +1001,3 @@ The former result can still be obtained with::
(`gh-16841 <https://github.com/numpy/numpy/pull/16841>`__)
-