Moving some discussion from https://github.com/nsidc/earthaccess/issues/877#issuecomment-2734544219 to it's own issue. Currently the conda-forge feedstock requires Zarr<3 and Virtualizarr>=1.2 https://github.com/conda-forge/earthdata-feedstock/blob/86aaa60fcacaf8a2ae3d8ce608f583b45a7d5fd1/recipe/meta.yaml#L39-L40 ``` - zarr >=2.12.0, <3.0.0a - virtualizarr >=1.2.0 ``` But virtualizarr>=1.3.3 will pin zarr>=3, which I think is going to cause some confusion. https://github.com/zarr-developers/VirtualiZarr/issues/392 https://github.com/zarr-developers/VirtualiZarr/compare/main..develop#diff-50c86b7ed8ac2cf95bd48334961bf0530cdc77b5a56f852c5c61b89d735fd711 From the pyproject.toml it looks like virtualizarr is actually an *optional dependency*, so maybe it should just be removed from the conda-forge recipe?https://github.com/nsidc/earthaccess/blob/18e947ec4660ccfe83038ebdd825ed1d08e5990d/pyproject.toml#L57-L64 Alternatively, not sure what work is needed to support Zarr v3 here?
Moving some discussion from #877 (comment) to it's own issue.
Currently the conda-forge feedstock requires Zarr<3 and Virtualizarr>=1.2
https://github.com/conda-forge/earthdata-feedstock/blob/86aaa60fcacaf8a2ae3d8ce608f583b45a7d5fd1/recipe/meta.yaml#L39-L40
But virtualizarr>=1.3.3 will pin zarr>=3, which I think is going to cause some confusion.
zarr-developers/VirtualiZarr#392
https://github.com/zarr-developers/VirtualiZarr/compare/main..develop#diff-50c86b7ed8ac2cf95bd48334961bf0530cdc77b5a56f852c5c61b89d735fd711
From the pyproject.toml it looks like virtualizarr is actually an optional dependency, so maybe it should just be removed from the conda-forge recipe?https://github.com/nsidc/earthaccess/blob/18e947ec4660ccfe83038ebdd825ed1d08e5990d/pyproject.toml#L57-L64
Alternatively, not sure what work is needed to support Zarr v3 here?