summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorSebastian Berg <sebastianb@nvidia.com>2022-12-05 10:45:56 +0100
committerSebastian Berg <sebastianb@nvidia.com>2022-12-05 13:00:27 +0100
commit37d95c80e3d4e277839d5ccf9189639c3a87bed5 (patch)
tree092ec020e21f850a5f562d302329622cceceef3e
parentd73e490159fc6d1e65dcb7acde5ae76ae420a019 (diff)
downloadnumpy-37d95c80e3d4e277839d5ccf9189639c3a87bed5.tar.gz
DOC: Remove last note from release note as per suggestion
It is a bit too obscure, but explaining that it happens for datetime unit conversions seems more detailed then useful. Updated to include a last non-indent line, which the release notes machinery doesn't like otherwise...
-rw-r--r--doc/release/upcoming_changes/22707.improvement.rst5
1 files changed, 2 insertions, 3 deletions
diff --git a/doc/release/upcoming_changes/22707.improvement.rst b/doc/release/upcoming_changes/22707.improvement.rst
index 95c67f1cc..1b8d4f844 100644
--- a/doc/release/upcoming_changes/22707.improvement.rst
+++ b/doc/release/upcoming_changes/22707.improvement.rst
@@ -1,9 +1,8 @@
New ``DTypePromotionError``
---------------------------
NumPy now has a new ``DTypePromotionError`` which is used when two
-dtypes cannot be promoted to a common one, for example raised by::
+dtypes cannot be promoted to a common one, for example::
np.result_type("M8[s]", np.complex128)
-Errors that occur while trying to find the correct promotion may raise a
-different error.
+raises this new exception.