-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
expose _to_temp_dataset / _from_temp_dataset as semi-public API? #4837
Comments
Related: There's some weirdness about xarray/xarray/core/parallel.py Lines 74 to 94 in bc35548
|
that's true. I guess for that there's the |
That seems very reasonable. To the extent the goal is "apply a function that takes a dataset to this dataarray", we could make a function that does exactly that and use |
yes, I think that would work, too. |
It used to preserve name, but now
This sounds like a fine idea to me. It's kind of the opposite of |
When writing accessors which behave the same for both
Dataset
andDataArray
, it would be incredibly useful to be able to useDataArray._to_temp_dataset
/DataArray._from_temp_dataset
to deduplicate code. Is it safe to use those in external packages (likepint-xarray
)?Otherwise I guess it would be possible to use
but that seems less efficient.
The text was updated successfully, but these errors were encountered: