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?
I'm going to re-open this, because I was going to request support for blosc2 in Zarr too. I'm not sure whether this depends on adding blosc2 to numcodecs or not, but even if it does it would be good to keep this issue open to disucss the ability to use it directly in zarr-python.
Activity
jhamman commentedon May 20, 2024
There are some active threads on the subject already:
Okay if we close this in favor of those open issues?
sanketverma1704 commentedon May 21, 2024
Also adding zarr-developers/numcodecs#463 to the list.
dstansby commentedon Jun 2, 2025
I'm going to re-open this, because I was going to request support for blosc2 in Zarr too. I'm not sure whether this depends on adding blosc2 to numcodecs or not, but even if it does it would be good to keep this issue open to disucss the ability to use it directly in zarr-python.
d-v-b commentedon Jun 2, 2025
In the interest of relaxing our numcodecs dependency, I would be interested in supporting it without adding it to numcodecs