From 43ce1ca68e819e1b92c2ec7790c64b41d469b9ef Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Kai=20M=C3=BChlbauer?= Date: Thu, 30 Jan 2025 13:35:26 +0100 Subject: [PATCH 1/3] finalize release notes --- doc/whats-new.rst | 32 +++++++++++++++++--------------- 1 file changed, 17 insertions(+), 15 deletions(-) diff --git a/doc/whats-new.rst b/doc/whats-new.rst index 76ed4c43882..4bd99a228a6 100644 --- a/doc/whats-new.rst +++ b/doc/whats-new.rst @@ -16,14 +16,21 @@ What's New .. _whats-new.2025.01.2: -v2025.01.2 (unreleased) ------------------------ +v2025.01.2 (Jan 31, 2025) +------------------------- + +This release brings non-nanosecond datetime and timedelta resolution to xarray, +sharded reading in zarr, suggestion of correct names when trying to access +non-existent data variables and bug fixes! -This release brings non-nanosecond datetime and timedelta resolution to xarray. -In the last couple of releases xarray has been prepared for that change. The -code had to be changed and adapted in numerous places, affecting especially the -test suite. The documentation has been updated accordingly and a new internal -chapter on :ref:`internals.timecoding` has been added. +Thanks to the 14 contributors to this release: +Deepak Cherian, Elliott Sales de Andrade, Jacob Prince-Bieker, Jimmy Westling, Joe Hamman, Joseph Nowak, Kai Mühlbauer, Mattia Almansi, Michael Niklas, Roelof Rietbroek, Salaheddine EL FARISSI, Sam Levang, Spencer Clark and Stephan Hoyer + +In the last couple of releases xarray has been prepared for allowing +non-nanosecond datetime and timedelta resolution. The code had to be changed +and adapted in numerous places, affecting especially the test suite. The +documentation has been updated accordingly and a new internal chapter +on :ref:`internals.timecoding` has been added. To make the transition as smooth as possible this is designed to be fully backwards compatible, keeping the current default of ``'ns'`` resolution on @@ -76,12 +83,9 @@ New Features :py:class:`pandas.DatetimeIndex` (:pull:`9965`). By `Spencer Clark `_ and `Kai Mühlbauer `_. -- :py:meth:`DatasetGroupBy.first` and :py:meth:`DatasetGroupBy.last` can now use ``flox`` if available. (:issue:`9647`) - By `Deepak Cherian `_. - -Breaking changes -~~~~~~~~~~~~~~~~ - +- Adds shards to the list of valid_encodings in the zarr backend, so that + sharded Zarr V3s can be written (:issue:`9947`, :pull:`9948`). + By `Jacob Prince_Bieker `_ Deprecations ~~~~~~~~~~~~ @@ -92,10 +96,8 @@ Deprecations data (:issue:`1621`, :pull:`9966`). By `Spencer Clark `_. - Bug fixes ~~~~~~~~~ - - Fix :py:meth:`DataArray.ffill`, :py:meth:`DataArray.bfill`, :py:meth:`Dataset.ffill` and :py:meth:`Dataset.bfill` when the limit is bigger than the chunksize (:issue:`9939`). By `Joseph Nowak `_. - Fix issues related to Pandas v3 ("us" vs. "ns" for python datetime, copy on write) and handling of 0d-numpy arrays in datetime/timedelta decoding (:pull:`9953`). From 35bf23290651ff1eb5f3054504d6bd961111af96 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Kai=20M=C3=BChlbauer?= Date: Thu, 30 Jan 2025 18:51:51 +0100 Subject: [PATCH 2/3] add contributors --- doc/whats-new.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/whats-new.rst b/doc/whats-new.rst index 4bd99a228a6..b838edc0c83 100644 --- a/doc/whats-new.rst +++ b/doc/whats-new.rst @@ -23,8 +23,8 @@ This release brings non-nanosecond datetime and timedelta resolution to xarray, sharded reading in zarr, suggestion of correct names when trying to access non-existent data variables and bug fixes! -Thanks to the 14 contributors to this release: -Deepak Cherian, Elliott Sales de Andrade, Jacob Prince-Bieker, Jimmy Westling, Joe Hamman, Joseph Nowak, Kai Mühlbauer, Mattia Almansi, Michael Niklas, Roelof Rietbroek, Salaheddine EL FARISSI, Sam Levang, Spencer Clark and Stephan Hoyer +Thanks to the 16 contributors to this release: +Deepak Cherian, Elliott Sales de Andrade, Jacob Prince-Bieker, Jimmy Westling, Joe Hamman, Joseph Nowak, Justus Magin, Kai Mühlbauer, Mattia Almansi, Michael Niklas, Roelof Rietbroek, Salaheddine EL FARISSI, Sam Levang, Spencer Clark, Stephan Hoyer and Tom Nicholas In the last couple of releases xarray has been prepared for allowing non-nanosecond datetime and timedelta resolution. The code had to be changed From be57bae74a6e36b7fe2bfd62da9f1488e0038a14 Mon Sep 17 00:00:00 2001 From: Spencer Clark Date: Thu, 30 Jan 2025 23:39:20 -0500 Subject: [PATCH 3/3] Tweak main what's new entry for time coding (#4) --- doc/whats-new.rst | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/doc/whats-new.rst b/doc/whats-new.rst index 74bbd3f5063..797afcc6bd8 100644 --- a/doc/whats-new.rst +++ b/doc/whats-new.rst @@ -70,8 +70,12 @@ eventually be deprecated. New Features ~~~~~~~~~~~~ -- Relax nanosecond datetime restriction in CF time decoding (:issue:`7493`, :pull:`9618`, :pull:`9977`, :pull:`9966`, :pull:`9999`). - By `Kai Mühlbauer `_ and `Spencer Clark `_. +- Relax nanosecond resolution restriction in CF time coding and permit + :py:class:`numpy.datetime64` or :py:class:`numpy.timedelta64` dtype arrays + with ``"s"``, ``"ms"``, ``"us"``, or ``"ns"`` resolution throughout xarray + (:issue:`7493`, :pull:`9618`, :pull:`9977`, :pull:`9966`, :pull:`9999`). By + `Kai Mühlbauer `_ and `Spencer Clark + `_. - Enable the ``compute=False`` option in :py:meth:`DataTree.to_zarr`. (:pull:`9958`). By `Sam Levang `_. - Improve the error message raised when no key is matching the available variables in a dataset. (:pull:`9943`)