Update doc/release/upcoming_changes/17029.compatibility.rst

1 files changed, 4 insertions, 13 deletions

diff --git a/doc/release/upcoming_changes/17029.compatibility.rst b/doc/release/upcoming_changes/17029.compatibility.rst
index 351b228a8..69069ce18 100644
--- a/doc/release/upcoming_changes/17029.compatibility.rst
+++ b/doc/release/upcoming_changes/17029.compatibility.rst
@@ -1,17 +1,9 @@
 Casting errors interrupt Iteration
 ----------------------------------
-NumPy sometimes has issues reporting errors during casting
-correctly. This is rare, since the vast majority of casts
-will never result in errors.
-However, in some cases of casting errors less of the result
-may be written back. The state of arrays involved in errors
-should *always* be considered undefined.
-Possible changes occur for:
-
-* Universal functions when casting is unsafe (rare)
-* Advanced index assignments
-* The lowlevel `numpy.nditer` API.
-
+When iterating while casting values, an error may stop the iteration
+earlier than before. In any case, a failed casting operation always
+returned undefined, partial results. Those may now be even more
+undefined and partial.
 For users of the ``NpyIter`` C-API such cast errors will now
 cause the `iternext()` function to return 0 and thus abort
 iteration.
@@ -20,4 +12,3 @@ It is necessary to check ``PyErr_Occurred()``, which
 may be problematic in combination with ``NpyIter_Reset``.
 These issues always existed, but new API could be added
 if required by users.
-