Add numcodecs entry point #21
Merged
Conversation
This file contains 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
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 adds the
numcodecs.codecsentry points to thenumcodecs_wasm_*Python packages. As part of that, all codec's codec IDs are updates in breaking releases to be unique and no longer clash with somenumcodecsbuiltin codecs.Additionally, this PR also adds encoded format versions to the codec configs (and where possible also encoded headers) to ensure that only compatible versions of the codec try to decode encoded data. Notably, these format versions are independent of the Rust crate / Python package versions, which are updated more frequently. Array-to-array codecs generally start with v1.0.0, since there is little that can be changed about the format, while array-to-bytes codecs start with v0.1.0.