Split napari-sparrow into sparrow (pipeline only) and napari-sparrow (plugin only)?
Closed this issue · 1 comments
SilverViking commented
The sparrow pipeline is useful in itself, without the dependency on napari.
Should we split up the current napari-sparrow package into two packages, one perhaps called "sparrow" and containing only the pipeline itself, and "napari-sparrow" (which has "sparrow" as a dependency) with only the sparrow plugin code for napari?
I think the resulting two packages would be more focussed, and probably cleaner.
SilverViking commented
It was decided by the main sparrow authors to keep the pipeline and the plugin code together in a single repo.