diff options
author | Stephan Hoyer <shoyer@google.com> | 2018-09-14 08:13:50 -0700 |
---|---|---|
committer | Stephan Hoyer <shoyer@google.com> | 2018-09-14 08:13:50 -0700 |
commit | 2967dd2b922718cb568ff675e73251fb47953b86 (patch) | |
tree | 0d9d620fc677f469fbf251896475bbf9e75e0425 | |
parent | 98916bb17b217b7aee52e7f7d31f16c99723085d (diff) | |
download | numpy-2967dd2b922718cb568ff675e73251fb47953b86.tar.gz |
DOC: release notes for expired NaT depreaction
-rw-r--r-- | doc/release/1.16.0-notes.rst | 15 |
1 files changed, 14 insertions, 1 deletions
diff --git a/doc/release/1.16.0-notes.rst b/doc/release/1.16.0-notes.rst index 0ba4636d9..8730c5860 100644 --- a/doc/release/1.16.0-notes.rst +++ b/doc/release/1.16.0-notes.rst @@ -42,6 +42,11 @@ Future Changes * NumPy 1.17 will drop support for Python 2.7. +Expired deprecations +==================== + +* NaT comparisons now return ``False`` without a warning, finishing a + deprecation cycle begun in NumPy 1.11. Compatibility notes =================== @@ -54,6 +59,15 @@ whenever the ``Scripts`` directory is in the path. Folks needing compatibility with earler versions of Numpy should run ``f2py`` as a module: ``python -m numpy.f2py [...]``. +NaT comparisons +--------------- +Consistent with the behavior of NaN, all comparisons other than inequality +checks with datetime64 or timedelta64 NaT ("not-a-time") values now always +return ``False``, and inequality checks with NaT now always return ``True``. +This includes comparisons beteween NaT values. For compatibility with the +old behavior, use ``np.isnat`` to explicitly check for NaT or convert +datetime64/timedelta64 arrays with ``.astype(np.int64)`` before making +comparisons. C API changes ============= @@ -149,4 +163,3 @@ modules, they are now python wrappers to the single `np.core/_multiarray_math` c-extension module. .. _`NEP 15` : http://www.numpy.org/neps/nep-0015-merge-multiarray-umath.html - |