-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
open_mfdataset fails with cftime index when using parallel and dask delayed client #6226
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
Update: It is Edit: Confirmed it is
|
Smaller repro import xarray as xr
import pickle
t = xr.cftime_range("20010101", "20010520")
pickle.loads(pickle.dumps(t)) Looks like pandas now passes xarray/xarray/coding/cftimeindex.py Line 313 in fe491b1
Might be pandas-dev/pandas#43188. So |
I just ran into the very same issue. Are you sure that this is a problem with pandas? I've had a look into the pandas changes between 1.3.X and 1.4.X. Apparently the
the problem is, that |
Thanks @antarcticrainforest -- I think that's exactly what @mathause is getting at. It seems fairly safe to add a new keyword argument to |
Are we expecting the |
Awesome, thanks @antarcticrainforest -- yes, it will always have an object |
Uh oh!
There was an error while loading. Please reload this page.
What happened?
A call to
open_mfdataset
withparallel=true
fails when using a dask delayed client with newer version ofcftime
andxarray
. This happens withcftime==1.5.2
andxarray==0.20.2
but notcftime==1.5.1
andxarray==0.20.2
.What did you expect to happen?
I expected the call to
open_mfdataset
to work without error withparallel=True
as it does withparallel=False
and a previous version ofcftime
Minimal Complete Verifiable Example
Relevant log output
Anything else we need to know?
It seems similar to previous issues with pickling #5686 which was fixed in
cftime
Unidata/cftime#252 but the tests in previous issues still work, so it isn't exactly the same.Environment
The text was updated successfully, but these errors were encountered: