Silence FututreWarning raised by xarray v2025.08.0 #3902
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
dcamron
added
Type: Maintenance
Contributor
Author
|
Thanks @dcamron |
dopplershift
added
the
backport
dopplershift
temporarily deployed
to
PR Backport
GitHub Actions
Inactive
Contributor
|
🏁 Successfully backported as #3908. 🏁 |
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.
Description Of Changes
In xarray v2025.08.0 a
FutureWarninghas been introduced in thexarray.mergefunction to inform the users that the default value for thecompatkeyword argument will change in the future.See pydata/xarray@d237a71.
The patch just modifies the current call to
xarray.mergeto pass explicitly the the current default value ofcompat.Checklist