Consistent packaging of napari backends in optional dependencies

brainglobe / BrainGlobe

General information, resources and dicussions for the BrainGlobe project.

https://brainglobe.info/

10 stars 1 forks source link

Consistent packaging of napari backends in optional dependencies #53

Open alessandrofelder opened 10 months ago

alessandrofelder commented 10 months ago

Across all packages, I would suggest we should:

always NOT ship any qt backend in [napari] optional dependencies to follow napari plugin best practice.
always ship napari[pyqt5] or whatever the napari default backend is, in the [dev] optional dependencies

alessandrofelder commented 10 months ago

We should also document this as part of https://github.com/brainglobe/brainglobe.github.io/issues/8

adamltyson commented 10 months ago

We need to ship napari in some way though right? Otherwise it complicates install for the user. What about:

Don't ship in the plugins themselves
Ship default backend in the metapackage

alessandrofelder commented 10 months ago

What about: ...

Happy with that. The drawback of this suggestion is if people install with pyside2 for some license-related reason, installing the metapackage will be complicated?

adamltyson commented 10 months ago

Happy with that. The drawback of this suggestion is if people install with pyside2 for some license-related reason, installing the metapackage will be complicated?

I guess the fallback here will just be to install the packages individually