zarr 3#108
Conversation
thewtex
commented
Feb 14, 2025
thewtex
commented
- COMP: Zarr Python 3 StoreLike support
- COMP: Use LocalStore for Zarr Python 3
- COMP: Remove dimension_deparator arg to MemoryStore
- Remove home-page from pyproject.toml
zarr.storage.BaseStore is not available in Zarr Python 3.
Replaces DirectoryStore.
Not available in Zarr Python 3.
Invalid field.
xarray-dataclasses version needed to be explicitly specified because pixi brings in 0.1.0 by default, which does not work. ipfsspec causes the solver to hang, but it is not needed, so it is removed. itk-filtering and dask-image duplicates were removed.
thewtex
force-pushed
the
zarr-3
branch
2 times, most recently
from
8cea275 to
de233f2
Compare
For Zarr-Python 3 compatibility.
|
Hi @thewtex, sorry for the radio silence. Is there part here you would like help with or we can share the workload a bit? |
|
@melonora thanks for the offer to help 🙏 We are currently blocked by astropenguin/xarray-dataclasses#240 , which prevents resolution of a valid dependency tree. A forked version could be published and used until it is resolved. |
|
I can have a look early next week |
|
Hey, just wanted to nudge a little bit - here on NixOS we are still waiting for this PR :). |
|
Apologies, I got overthrown later with lab work. I had a look at the repo and the problem is now that the person owning the repository seems to have deleted all the code on main right now. I will pull the last working release and work from there. |
|
@doronbehar The fork on my branch is I think almost ready after I fix the conflicts. I would like to have one look with @thewtex before releasing from my fork, but then after this we can adjust this PR and get it merged. As said before, from the original repository all the code on main got deleted. It seems like the maintainer was in the process of moving to the use of |
|
@doronbehar I discussed with @thewtex and we think it is best to move the fork to the |
|
CC @ianhi |
|
@doronbehar Just to update, I am trying to get the repository in the xarray-contrib organization right now, see xarray-contrib/xarray-contrib#16 |
|
@doronbehar @thewtex |
|
@melonora woohoo! 🎇 It looks like zarr-python 3 issues? |
|
hmm can't see that conversation, but I will check later |
|
Todo:
|
And corresponding spatial-image version bump to avoid conflicts with xarray-dataclasses.
- Add asyncio import for v3 async store API - Update check_valid_ngff() to handle both v2 and v3 store APIs - Method 1: Try accessing via zarr group attrs (works for both) - Method 2: Try v2 dict-like store access for consolidated metadata - Method 3: Try v3 async store API with prototype parameter - Handle different buffer/bytes formats between versions - Gracefully fallback between methods to support both versions
3 participants
