Adding `open_datatree` backend-specific keyword arguments

pydata / xarray

N-D labeled arrays and datasets in Python

https://xarray.dev

Apache License 2.0

3.5k stars 1.04k forks source link

Adding `open_datatree` backend-specific keyword arguments #9199

Open aladinor opened 1 week ago

aladinor commented 1 week ago

[x] Closes ##9135
[ ] User visible changes (including notable bug fixes) are documented in whats-new.rst
[ ] New functions/methods are listed in api.rst

keewis commented 6 days ago

you might want to rebase / cherry-pick the two commits for this PR onto main, so there's only those two commits to check in this PR. If you don't have any idea how to do that, I can do it for you.

keewis commented 6 days ago

so unfortunately I can't push to your repository, because it is a fork of someone else's fork (and I'm not a maintainer on that fork). To fix that, you can either request someone from github to "reroute" your fork, or you can pull all your branches to local (I'm sure you did already), delete the repository and fork again. I'm not sure what would happen to this PR, though.

keewis commented 6 days ago

if you want to fix up this PR (which is usually much quicker), you can also follow the steps yourself. Basically, what you do is:

git switch main
git pull
git switch open-dtree-kwargs
# rewind to main
git reset --hard HEAD~60
git merge main
# apply the two commits that were added in this PR
git cherry-pick 179b6960c6e2f49b38eda13a97d977a72bcb5990
git cherry-pick 563b5dbda4dabd253c38c9ca577015224447314f
git push --force