-
-
Notifications
You must be signed in to change notification settings - Fork 27
Check with Xarray #904
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
Comments
Our tests are failing since the env doesn't contain
It looks like the |
Without that you'd have to make |
We have actually. You need to |
|
I don't think that this is a good idea if we want people to actually use it |
We would warn and then gracefully fall back to old behavior. That seems better to me than failing hard. |
People mostly ignored the deprecation warning even though it was very noisy, I don't think that this would be any different. |
Ah yes, we missed adding |
Well, like in that case it was pretty disruptive and people were sad. We've learned that people don't like being disrupted. I'm inclined to give them the warning information for now but also gracefully fall back. I don't want to force people's code to break in order to get them to upgrade; at least not yet. |
We had another subtle issue from |
This is a known issue dask/dask#10996 |
More failures :) See https://github.com/pydata/xarray/actions/runs/8288508222/job/22683171250?pr=8790
|
We'd like to make sure that Xarray works with the new version of dask dataframe
I took a quick look at the codebase, and it looks like they're using
dd.from_dask_array
, so everything should be ok. It might be worth checking with them explicitly though. cc @dcherianThe text was updated successfully, but these errors were encountered: