Closed RondeauG closed 8 months ago
Let's wait for https://github.com/Ouranosinc/xclim/pull/1664 before we finish this PR.
The problem with Python3.12 is quite silly. Pushing a fix in a few mins.
I can push something that ensures the new xrfreq is used when we open catalogs (and parse them).
Last commit added a ensure_new_xrfreq
function to utils
. It is used when opening a catalog and in parse_directory
. This means that legacy frequencies either in the paths or in the catalogs shouldn't be a problem.
Running on MRCC5-disponible, our largest catalog, my n=1
test finds that the opening time has increased by 6%. I decided that this was small enough not to require further optimization or skipping options.
I'll be releasing xclim v0.48.2 today!
This PR is waiting on the newest patch release from conda-forge. Should be available later today.
xclim>=0.48.0
ou xclim>=0.48.2
?
Check out this pull request on
See visual diffs & provide feedback on Jupyter Notebooks.
Powered by ReviewNB
Pull Request Checklist:
number
) and pull request (:pull:number
) has been added.What kind of change does this PR introduce?
pandas/xarray/xclim
Does this PR introduce a breaking change?
xscen
now requirespandas >= 2.2
extract_dataset, compute_indicators
) will now return the new nomenclature.frequency --> xrfreq/timedelta
will now only result in the new nomenclature for hours (lower caseh
).Other information: