Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
support
chunks
inopen_groups
andopen_datatree
#9660support
chunks
inopen_groups
andopen_datatree
#9660Changes from 2 commits
fe95b16
3bfbc3a
f4abb01
b0458aa
4dbd91e
11850fd
a71f5e2
6d3deed
7f770cf
05efaf6
f9fee40
2e10bdc
a4e99c6
3e8b80c
cf1a6b0
114c4dc
9eac19d
446a53d
5b36701
66616f7
843b2fc
8950841
4d93ada
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
backend_tree
should have been created usingdatatree_from_dict_with_io_cleanup
, so one way to handle this could be just to copy over the_close
attribute from every node ofbackend_tree
?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the question is, do we even need that here? I copied this from
open_dataset
where this is explicitly set, but sincedatatree_from_dict_with_io_cleanup
does this already we might be able to just remove it?The only reason why I kept the commented-out line is to discuss whether the shift in paradigm (have the backend set
_close
vs. do it for all backends the same way) is intentional, and if we should do the same foropen_dataset
.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree it would be nice to remove this, I'm just worried that mapping over the each
.dataset
might not properly propagate._close
(does it? should it?)There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It does not (I think), so I'm explicitly copying it over. So far that doesn't appear to cause anything to break.