You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since both the APIs and the container (on-disk) formats changed between Blosc and Blosc2, it might be best to support Blosc2 as a new codec.
Is this a good idea? How would I go about proposing this officially? At the technical level, I assume that actually writing the specification and opening a pull request would be a step towards receiving feedback?
The text was updated successfully, but these errors were encountered:
Zarr supports the Blosc library as a codec https://zarr-specs.readthedocs.io/en/latest/v3/codecs/blosc/v1.0.html . Blosc is now somewhat outdated, and a successor Blosc2 exists. It would be nice if Blosc2 was supported as a codec as well.
Since both the APIs and the container (on-disk) formats changed between Blosc and Blosc2, it might be best to support Blosc2 as a new codec.
Is this a good idea? How would I go about proposing this officially? At the technical level, I assume that actually writing the specification and opening a pull request would be a step towards receiving feedback?
The text was updated successfully, but these errors were encountered: