-
Notifications
You must be signed in to change notification settings - Fork 51
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
admin/include-fsspec-dep-for-czi-in-readme #433
Conversation
Codecov Report
@@ Coverage Diff @@
## main #433 +/- ##
==========================================
- Coverage 94.03% 93.92% -0.12%
==========================================
Files 46 46
Lines 3972 3997 +25
==========================================
+ Hits 3735 3754 +19
- Misses 237 243 +6
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
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.
That works!
Better than nothing for sure, but a fresh install will get So it's just situations where someone upgrades BTW Is it worth carving an aicsimageio/aicsimageio/aics_image.py Lines 214 to 234 in 93559b1
|
Great recommendation. Will do that tonight! |
"czi": [ | ||
"fsspec>=2022.7.1", | ||
# "aicspylibczi>=3.0.5", # excluded for licensing reasons | ||
], |
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 line is giving me pause. You can install [czi]
and not get czi support? I'm not sure if this is helping.
Description
Sorta solves #431?? We can't really fully solve it because forcing everyone to upgrade their fsspec envs may result in dependency management for them. The only reader that broke with the recent fsspec change was CZI. So updating the CZI install docs to include the fsspec upgrade.
Pull request recommendations:
Thanks for contributing!
cc @psobolewskiPhD