Exclude fsspec 2023.9.0 #307
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
joshmoore
approved these changes
Sep 15, 2023
There was a problem hiding this comment.
Thanks, @will-moore. Interested to see how the filter list looks over time...
I'll create an immediate 0.8.1
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In https://github.com/ome/ome-zarr-py/pull/301/files we needed to avoid the latest fsspec version
fsspec 2023.9.0due to avoid fsspec/filesystem_spec#1357 (also reported at #304).The fix at fsspec/filesystem_spec#1358 is merged and should be included in the next fsspec release so we only need to exclude the current release version.
This makes the corresponding change to setup.py