(fix): blosc v2 typesize in config
#94
Merged
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
ilan-gold
commented
Apr 9, 2025
LDeakin
approved these changes
Apr 9, 2025
Member
LDeakin
left a comment
LDeakin
left a comment
There was a problem hiding this comment.
Does zarr-python serialise the typesize now on V2 blosc-encoded arrays?
Collaborator
Author
|
|
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.
Handling the new
typesizein the declaration of the object: zarr-developers/numcodecs#713. I don't think we need to worry about the object being declared withtypesizein v2 (and for now,zarrsdoesn't seem to support it anyway)