-
-
Notifications
You must be signed in to change notification settings - Fork 329
Add StoreV3 support to creation.py (zarr v3 support part 5) #897
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
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Define the StoreV3 class and create v3 versions of most existing stores Add a test_storage_v3.py with test classes inheriting from their v2 counterparts. Only a subset of methods involving differences in v3 behavior were overridden.
Codecov Report
@@ Coverage Diff @@
## master #897 +/- ##
==========================================
- Coverage 99.94% 98.59% -1.35%
==========================================
Files 32 34 +2
Lines 11216 13486 +2270
==========================================
+ Hits 11210 13297 +2087
- Misses 6 189 +183
|
2af0045
to
dd7d237
Compare
dd7d237
to
8e3c443
Compare
8e3c443
to
b0eaa37
Compare
zarr_version should not be in the array metadata, only the base store metadata compressor should be absent when there is no compression
classmethods adapted from zarrita code
avoid pytest error about missing fixture fix flake8 error related to zarr_version fixture
update hexdigests
Specifically, we want to be able to infer the dimension_separator from the store if possible
b0eaa37
to
e4ce79f
Compare
closing, these commits along with additional fixes and tests are incorporated in #898 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR builds on #896 adding v3 support to the high-level array creation routines.
TODO: