maint: bump minimum dependency versions according to policy#11231
maint: bump minimum dependency versions according to policy#11231jhamman merged 14 commits intopydata:mainfrom
Conversation
for more information, see https://pre-commit.ci
…y into maint/202603-version-bumps
for more information, see https://pre-commit.ci
…y into maint/202603-version-bumps
for more information, see https://pre-commit.ci
| elif zarr_format == 3: | ||
| # specifying codecs in zarr_format=3 requires importing from zarr 3 namespace | ||
| from zarr.registry import get_codec_class | ||
| import zarr |
There was a problem hiding this comment.
these are the minimal required changes to get this new environment spec passing in CI. A more comprehensive cleanup of the Zarr backend and tests can be found in #11232
|
This is ready for a review. I don't believe the failing flaky tests are related to any changes here. |
|
Yeah apparently |
Yeah I guess so if you want to merge before Q2 |
…y into maint/202603-version-bumps
|
I've reverted the numpy 2 changes for now. |
| - hypothesis | ||
| - pytz | ||
| - pytest-reportlog | ||
| - pyarrow # transitive dependency of dask.dataframe, not an xarray dependency |
There was a problem hiding this comment.
Why do we care about dask.dataframe?
There was a problem hiding this comment.
we test exporting datasets to dask-dataframe.
doc/whats-new.rst
Outdated
|
|
||
| Breaking Changes | ||
| ~~~~~~~~~~~~~~~~ | ||
| The minimum versions of some dependencies were changed: |
There was a problem hiding this comment.
let's call out the Zarr bump and clarify that Zarr 2 formats are still readable.
4 participants
This PR updates our minimum dependency versions. There are a number of notable bumps in here:
"numpy>=2.1"zarr>=3.0"
User visible changes (including notable bug fixes) are documented in
whats-new.rstSee #11232 for the larger zarr3 cleanup