Closed jdeschamps closed 1 year ago
Hi @jdeschamps, sorry you encountered issues! The problem is caused by a mismatch with the dependency that I thought I would be able to work on silently without messing up anyone's system, so you just got unlucky and tried to use blik
when it's broken :P Yes, pinning dependencies for now is a good idea.
I'm currently waiting for napari==0.4.17
(which should come in the coming 2 weeks hopefully) in order to push several updates that depend on it and make a new release. I will update you once that happens!
For the time being, forcing naaf==0.2.3
as you found out should be enough to help.
Alright, if napari==0.4.17
is really that close, then I understand it makes no sense to make an in-between version.
Thanks!
Hi!
A collaborator tried to use blik and had some issues. I could reproduce the errors with their data. I encountered problems with some of the dependencies, both when starting napari and then when starting the reader plugin.
1) Related to imageio==2.22.1 that prevents napari from starting. i would suggest to pin either
imageio!==2.22.1
insetup.cfg
or suggesting topip install "napari[all]==0.4.15
in the Readme.2)
naaf
version 0.3.1 doesn't havenaaf.data
submodule:Maybe you could pin
naaf>=0.2.2, <=0.2.3
in a new version at least until you merge a branch compatible withnaaf>=0.3.0
?