-
Notifications
You must be signed in to change notification settings - Fork 1
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
Relax dependency versions? #32
Comments
Hey @haesleinhuepf, |
Hi @bauerdavid , just one thing because I'm not sure if I was clear. I hope that your plugin supports older versions (napari<=0.4.15), because the devbio-napari distribution I mentioned also doesn't support 0.4.16. Thus, I don't care much about 0.4.16, I care more about 0.4.11-0.4.15 because they are quite common in the field. The problems in 0.4.16 will hopefully go away with 0.4.17 at some point ;-) Thanks! |
That's why I have this in devbio-napari: |
Yup, you were clear, but of course I misread it... Unfortunately if I recall correctly, there were some functionalities which depend heavily on newer versions of napari. But I will check whether that's possible. |
No pressure. Thanks for the feedback! 🌞 |
I reverted napari to 0.4.11, but didn't spend too much time with it, because I realized that supporting all these versions of napari might(!) require a huge amount of work, mostly because of the bounding box layer. Between different releases napari sometimes changes its package structure, and (of course) built-in layers are changed accordingly, not to mention other changes in these layers. If we would want to make the I'm afraid I won't be able to make this happen. But if you or anyone else wanted to take a look at this and check if it's feasible, I would be more than happy to collaborate 🙂 As for vispy, I am thinking maybe the easiest solution would be to lift the version restriction, as it is not related to the plugin, but to napari, and having |
No problem. I really didn't want to create any pressure.
Just out of curiosity: did you upload that code to GitHub? I would like to take a look. Thanks again for considering! |
Sure! This is the commit: da82a5f |
Hey @haesleinhuepf, David |
Hey @haesleinhuepf,
Best wishes, |
Awesome, big thanks for working on this @bauerdavid ! |
Hi @bauerdavid ,
first of all congrats to this great plugin! Here in Dresden many people are using it. I would like to add it to a plugin-collection: devbio-napari to ship it together with other plugins to collaborators. However, there is a tiny issue with pinned dependencies in napari-nd-annotator, which limits who can install it.
Would it be possible to change
napari == 0.4.15
tonapari <= 0.4.15
in these two places?napari-nD-annotator/setup.cfg
Line 44 in a4caf6a
Furthermore, would it be possible to change
vispy == 0.9.6
tovispy <= 0.9.6
in this place?napari-nD-annotator/setup.cfg
Line 45 in a4caf6a
Thanks for considering! Let me know what you think.
Best,
Robert
The text was updated successfully, but these errors were encountered: