Skip to content

Conversation

@btschwertfeger
Copy link
Owner

@btschwertfeger btschwertfeger commented Nov 13, 2025

Setting the current default values explicitly ensures future releases of xarray won't break cmethods.

Closes #178

@btschwertfeger btschwertfeger added this to the Upcoming Release milestone Nov 13, 2025
@btschwertfeger btschwertfeger self-assigned this Nov 13, 2025
@btschwertfeger btschwertfeger enabled auto-merge (squash) November 13, 2025 08:04
@codecov
Copy link

codecov bot commented Nov 13, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 95.82%. Comparing base (2c5814f) to head (fd17d9b).
⚠️ Report is 1 commits behind head on master.

Additional details and impacted files

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #179   +/-   ##
=======================================
  Coverage   95.82%   95.82%           
=======================================
  Files           7        7           
  Lines         335      335           
=======================================
  Hits          321      321           
  Misses         14       14           
Flag Coverage Δ
unittests 95.82% <100.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines Coverage Δ
cmethods/core.py 90.27% <100.00%> (ø)
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@btschwertfeger btschwertfeger merged commit 6b01a81 into master Nov 13, 2025
39 of 40 checks passed
@btschwertfeger btschwertfeger deleted the 178-futurewarning-xarraymerge-will-change branch November 13, 2025 08:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

FutureWarning: xarray.merge will change

2 participants