Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Zarr V2 vs V3 #17

Open
TomNicholas opened this issue Mar 8, 2024 · 2 comments · May be fixed by #182
Open

Zarr V2 vs V3 #17

TomNicholas opened this issue Mar 8, 2024 · 2 comments · May be fixed by #182
Labels
zarr-python Relevant to zarr-python upstream

Comments

@TomNicholas
Copy link
Collaborator

What needs to be done here?

@TomNicholas
Copy link
Collaborator Author

Ideally we would be able to import Zarr objects from zarr-python that help us navigate the differences between v2 and v3

@TomNicholas
Copy link
Collaborator Author

So Zarr v3 was released last week (it's on PyPI, and can be installed by specifying --pre with pip install). This means we can start the process of refactoring virtualizarr to use the v3 zarr-python library for some internal abstractions.

In particular I want to replace the virtualizarr.zarr.ZArray class. I haven't really looked at the v3 code much at all yet, but I'm hoping there is some drop-in for the ZArray class that can smoothly handle the difference between Zarr v2 and v3 arrays for us. (And if there's not we should be making suggestions upstream.)

@ghidalgo3 ghidalgo3 linked a pull request Jul 10, 2024 that will close this issue
9 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
zarr-python Relevant to zarr-python upstream
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant