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

Vendor zarr imports #285

Merged
merged 9 commits into from
Jan 3, 2025
Merged

Vendor zarr imports #285

merged 9 commits into from
Jan 3, 2025

Conversation

mpiannucci
Copy link
Contributor

@mpiannucci mpiannucci commented Dec 3, 2024

Xpublish should be zarr python version agnostic, this is the first step in getting xpublish running with zarr python 3

@mpiannucci
Copy link
Contributor Author

pre-commit.ci autofix

@mpiannucci mpiannucci changed the title Protect zarr imports Vendor zarr imports Dec 3, 2024
@@ -49,9 +49,9 @@ def test_invalid_encoding_chunks_with_dask_raise():
data = dask.array.zeros((10, 20, 30), chunks=expected)
ds = xr.Dataset({'foo': (['x', 'y', 'z'], data)})
ds['foo'].encoding['chunks'] = [8, 5, 1]
with pytest.raises(ValueError) as excinfo:
Copy link
Contributor Author

@mpiannucci mpiannucci Dec 4, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Running against the latest xarray, this throws an TypeError because region in the xarray dask check is None so it cant even compute the check

@mpiannucci mpiannucci marked this pull request as ready for review December 4, 2024 01:02
@mpiannucci mpiannucci requested a review from jhamman December 4, 2024 01:03
@mpiannucci mpiannucci requested a review from abkfenris January 3, 2025 18:09
@mpiannucci mpiannucci merged commit c64d6bc into main Jan 3, 2025
12 checks passed
@mpiannucci mpiannucci deleted the matt/protect-zarr-imports branch January 3, 2025 18:31
@mo-dkrz
Copy link

mo-dkrz commented Jan 26, 2025

Dear @abkfenris
It seem merging this PR has fixed the issue with python-zarr version 3, so I was wondering could you please run the release workflow and publish the pypi for the new version? thanks in advance

@abkfenris
Copy link
Member

Hi @mo-dkrz , I think @mpiannucci had something else that they wanted to land/let things settle with external libraries before cutting a new release.

@mpiannucci
Copy link
Contributor Author

I think this is fine now that zarr 3 is out. We should add a CI test for it though to make sure

@mo-dkrz
Copy link

mo-dkrz commented Jan 28, 2025

Thanks for explanation

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants