-
Notifications
You must be signed in to change notification settings - Fork 8
Upgrade zarr-python dependency to 3.0 #275
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
base: main
Are you sure you want to change the base?
Conversation
@aliddell I noticed that your editor uses 8-spaces indentation. We use black-format and 4-space indentation in this repo. Please see the contributing guide for information about setting up the styling and linting tools. |
) | ||
) | ||
img_arr[...] = data |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This breakage seems unintended from upstream discussion. We can revert after zarr-developers/zarr-python#2819 is released.
We still have
which looks like an internal issue in tifffile. Two more (both variants of
There are likely references to the NGFF version that don't handle "0.5" or have it as an option. That needs tests. |
Thanks @aliddell! I believe the tifffile error is due to how zarr changed its interface to implement third-party storage types. We either need to wait for cgohlke/tifffile#282 or change the way we implement OME-TIFF support. However I think it's a relatively self-contained issue, and as long as the OME-Zarr part is migrated, we can continue to work on bridging acquire-zarr and iohub via Zarr v3/OME-Zarr v0.5. |
@@ -8,6 +8,7 @@ | |||
|
|||
import numpy as np | |||
import zarr | |||
import zarr.storage |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this import necessary?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it might not be. If I remove it, my IDE complains in line 49, but it doesn't seem to break anything.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it's an implementation detail of the language server you are using.
* use fsspec as a wrapper for ZarrTiffStore * update deprecated readers and tests * document the helper function * add back the binary check after a flag * use kwarg for file mode in reader * restore dtype attribute * restore opening zarr with dask * stringify path name * remove redundant dtype
it doesn't matter what the order is
@@ -392,6 +398,7 @@ def test_rename_channel(channels_and_random_5d, arr_name, new_channel): | |||
assert dataset.metadata.omero.channels[0].label == new_channel | |||
|
|||
|
|||
# @pytest.mark.skip(reason="broken") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@aliddell This test does pass now. Can you document why it was marked 'broken'?
No description provided.