summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMatti Picus <matti.picus@gmail.com>2022-12-05 15:25:15 -0500
committerGitHub <noreply@github.com>2022-12-05 15:25:15 -0500
commit7375ee6b5817b26182bb98f37f71b8f28acf8a77 (patch)
tree8e2b7faa1fb0c14aa757eaaaa9d8f9854b2cbfd7
parentd9b75bcc944a71240cba6d684735bf3e7fd8468b (diff)
downloadnumpy-7375ee6b5817b26182bb98f37f71b8f28acf8a77.tar.gz
DOC: typo
-rw-r--r--doc/release/upcoming_changes/22707.expired.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/release/upcoming_changes/22707.expired.rst b/doc/release/upcoming_changes/22707.expired.rst
index b32b783d2..496752e8d 100644
--- a/doc/release/upcoming_changes/22707.expired.rst
+++ b/doc/release/upcoming_changes/22707.expired.rst
@@ -6,7 +6,7 @@ The ``==`` and ``!=`` operators on arrays now always:
have incompatible shapes (``np.array([1, 2]) == np.array([1, 2, 3])``).
* return an array of all ``True`` or all ``False`` when values are
fundamentally not comparable (e.g. have different dtypes). An example
- is ``np.array(["a"]) == np.array([1])`.
+ is ``np.array(["a"]) == np.array([1])``.
This mimics the Python behavior of returning ``False`` and ``True``
when comparing incompatible types like ``"a" == 1`` and ``"a" != 1``.