Replies: 1 comment 1 reply
-
|
Sorry for the friction @ilan-gold! You're absolutely right that the API changed in #2784. 🤦 I think we are still adjusting to the fact that CodecPipeline actually has implementations outside of Zarr Python! This is a good thing! |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
So @rabernat this sort of thing (including, say, the |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello! It seems that
3.0.3contained a breaking change to theCodecPipelineAPI but on a patch version: #2784. I would have thought theCodecPipelinewould obey semver since it is a public API for people implementing pipelines.Clarifying this situation would help us in https://github.com/ilan-gold/zarrs-python give a guarantee of stability and/or take steps to ensure we are running tests upon the release of every zarr (if there is no guarantee).
Beta Was this translation helpful? Give feedback.
All reactions