You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Replace DeprecationWarning with FutureWarning (#11112)
When deprecating functionality, xarray has sometimes used ``FutureWarning`` and sometimes used ``DeprecationWarning``. ``DeprecationWarning`` is not intended to be visible to end-users so this PR switches to using ``FutureWarning`` everywhere
Copy file name to clipboardExpand all lines: doc/get-help/faq.rst
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -423,7 +423,7 @@ How stable is Xarray's API?
423
423
424
424
Xarray tries very hard to maintain backwards compatibility in our :ref:`api` between released versions.
425
425
Whilst we do occasionally make breaking changes in order to improve the library,
426
-
we `signpost changes <https://docs.xarray.dev/en/stable/contributing.html#backwards-compatibility>`_ with ``DeprecationWarnings`` for many releases in advance.
426
+
we `signpost changes <https://docs.xarray.dev/en/stable/contributing.html#backwards-compatibility>`_ with ``FutureWarnings`` for many releases in advance.
427
427
(An exception is bugs - whose behaviour we try to fix as soon as we notice them.)
428
428
Our `test-driven development practices <https://docs.xarray.dev/en/stable/contributing.html#test-driven-development-code-writing>`_ helps to ensure any accidental regressions are caught.
429
429
This philosophy applies to everything in the `public API <https://docs.xarray.dev/en/stable/getting-started-guide/faq.html#what-parts-of-xarray-are-considered-public-api>`_.
0 commit comments