-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
xarray - compatibility with latest versions #275
Comments
I can rustle up some RSE effort to look at this, but it might not be for a little while. |
@ZedThree that would be awesome. I don't have time to look myself. It's not super urgent as the last good version (xarray-2022.6.0) is fine for now. |
Would be interesting to see if the performance regression is fixed by the latest xarray release - pydata/xarray#7824 may help things. |
Output of pytest with xarray 2023.7.0 and python 3.12:
Good thing is no errors. And there is also some potential to improve performance ;-) |
I have had problems with this issue for a new installation of a python |
Hi @mrhardman ! This should be fixed by this PR #303 but there is something odd going on with python 3.12 and 3.13: They segfault or hang on the Github CI somewhere inside Dask and Numpy. Python 3.13 works fine locally. Which version of python are you using? |
The version was python 3.13.0. I can try to reproduce the error with a fresh |
I also see random segfaults during the tests on fedora. I have not managed to figure out what is going on. |
Some change in xarray-2022.9.0 introduced a significant performance regression (see #213 (comment)). Possibly something related to the default option used to combine coordinates/metadata when combining two DataArrays/Datasets.
There also seem to be occasional errors when using the latest xarray versions - possibly some deprecated things that we need to update in xBOUT?
It is not good to not be able to use the latest versions of xarray. It would be really good if someone could work out what these issues are and how to fix them!
#234, #220, #213 are related.
The current workaround is to restrict xarray to versions <2022.9.0 #274.
The text was updated successfully, but these errors were encountered: