You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are currently getting these deprecation warnings:
DeprecationWarning: datetime64_to_cdftt2000 will eventually be phased out. Instead, datetime64 types will automatically be converted into a CDF time type. If you do not wish datetime64 arrays to be converted, cast them to a different type prior to calling xarray_to_cdf()
even when leaving out the keyword argument in the call. This is because there is a default keyword argument still in the signature which makes this case always hit.
"datetime64_to_cdftt2000 will eventually be phased out. Instead, datetime64 types will automatically be converted into a CDF time type. If you do not wish datetime64 arrays to be converted, cast them to a different type prior to calling xarray_to_cdf()",
DeprecationWarning,
stacklevel=2,
)
I think you might be able to add a **kwargs catch-all here for the deprecation warning and see if datetime64_to_cdftt2000 is in kwargs and issue the deprecation warning then.
The text was updated successfully, but these errors were encountered:
We are currently getting these deprecation warnings:
even when leaving out the keyword argument in the call. This is because there is a default keyword argument still in the signature which makes this case always hit.
cdflib/cdflib/xarray/xarray_to_cdf.py
Lines 1003 to 1008 in 88ba11e
I think you might be able to add a
**kwargs
catch-all here for the deprecation warning and see ifdatetime64_to_cdftt2000
is in kwargs and issue the deprecation warning then.The text was updated successfully, but these errors were encountered: