diff options
| -rw-r--r-- | doc/release/upcoming_changes/22707.compatibility.rst | 6 | ||||
| -rw-r--r-- | doc/release/upcoming_changes/22707.expired.rst | 2 |
2 files changed, 4 insertions, 4 deletions
diff --git a/doc/release/upcoming_changes/22707.compatibility.rst b/doc/release/upcoming_changes/22707.compatibility.rst index 509d20804..8c9805f37 100644 --- a/doc/release/upcoming_changes/22707.compatibility.rst +++ b/doc/release/upcoming_changes/22707.compatibility.rst @@ -1,4 +1,4 @@ * When comparing datetimes and timedelta using ``np.equal`` or ``np.not_equal`` - numpy previously allows the comparison with ``casting="unsafe"``. - This operation now fails (before the casting check), ``dtype=`` can restore - the old behavior, but we do not recommend it. + numpy previously allowed the comparison with ``casting="unsafe"``. + This operation now fails. Forcing the output dtype using the ``dtype`` + kwarg can make the operation succeed, but we do not recommend it. diff --git a/doc/release/upcoming_changes/22707.expired.rst b/doc/release/upcoming_changes/22707.expired.rst index bf1985b0e..b32b783d2 100644 --- a/doc/release/upcoming_changes/22707.expired.rst +++ b/doc/release/upcoming_changes/22707.expired.rst @@ -8,6 +8,6 @@ The ``==`` and ``!=`` operators on arrays now always: fundamentally not comparable (e.g. have different dtypes). An example is ``np.array(["a"]) == np.array([1])`. -For a long time these gave ``DeprecationWarning`` or ``FutureWarning``. This mimics the Python behavior of returning ``False`` and ``True`` when comparing incompatible types like ``"a" == 1`` and ``"a" != 1``. +For a long time these gave ``DeprecationWarning`` or ``FutureWarning``. |