refactor: extract legacy codec interfaces into zarr-codec - #4319
Draft
d-v-b wants to merge 1 commit into
Draft
Conversation
Assisted-by: Codex:GPT-6
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #4319 +/- ##
==========================================
+ Coverage 94.21% 94.23% +0.01%
==========================================
Files 92 92
Lines 12871 12880 +9
==========================================
+ Hits 12127 12137 +10
+ Misses 744 743 -1 🚀 New features to boost your workflow:
|
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
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.
Summary
AI-written creation of a
zarr_codecsubpackage that contains our codec APIs. That subpackage would be published and versioned separately fromzarr. All currentzarrfunctionality is accessible by importing stuff from thezarr_codec.legacymodule.This PR does not change
zarr. Makingzarrdepend onzarr-codecwould happen later, after we stand up the package. This will allow us to develop a new codec API while keeping our old one available indefinitely.The original AI-written PR is here: d-v-b#326
For reviewers
we can bikeshed the layout of
zarr-codec.legacy, or discuss the motivation for subpackaging the codec API. In case you want to chat about this direction more conversationally, I started a Zulip thread#Zarr-Python > subpackaging store and codec APIs.See also
Author attestation
TODO
docs/user-guide/*.mdchanges/