Pandas and Xarray deprecations #1374
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
erogluorhan
approved these changes
Sep 16, 2025
Member
erogluorhan
left a comment
erogluorhan
left a comment
There was a problem hiding this comment.
Thanks very much for doing this!
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #1371
Overview
Addresses deprecations from Pandas and Xarray causing warnings and/or failures in the test suite.
In particular, the use of several Pandas offset aliases (see here for more info from Pandas) and the use of Dataset.dims as a mapping from dimension names to lengths (see here).
It's worth noting that I didn't make an effort to make these changes backwards compatible with versions of Pandas and Xarray before the suggested replacements existed. For Pandas, this has been working since v2.2.0 released in January, 2024 and for Xarray
Dataset.sizeshas been around since well before they adopted CalVer so probably less of a concern. Not sure if you all have thoughts / policies on this.PR Checklist
General