-
Notifications
You must be signed in to change notification settings - Fork 9
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
napari-installation-manager
prototype
#10
Comments
Working on Phase 1) New package for the backend ( Also this packages for now is pure python only to keep the base environment simple. |
curious where we are on the prototype. Are we still on track to releasing the package after switching to a unified approach between installation and plugin manager? |
Hi @potating-potato still working on this, I should be finishing this week, with a bit of next one. I can start working on the UI with @ppwadhwa next week. |
@jaimergp, since Gonzalo is out, is there anything you can help with here? I am ok if we have to trade off plugin migration work and other things |
Sure I can move my priorities around, but I don't have access to what Gonzalo has done so far. Is it worth it to start from scratch? |
oh noo... by any chance can you ask him to push what he has so far? if we can't reach him then I would say it is not worth it starting from scratch |
Sorry for the delay, added the PR here #34 Updating tests today! |
I am going to close this story in favor of the other split stories in the project board |
The installation-manager development plan is divided in three phases that will be rolled out sequentially. It's designed as an application-agnostic tool that can be customized to support the napari use case.
Phase 1: CLI-only
Tool 1: constructor-updater (backend)
Python application and CLI tool to be installed in
base
environment.Tool 2: constructor-updater (frontend)
Python application providing API to be used by napari (and other tools). Communicate with the constructor-updater backend. To be installed in the
application environment
.Phase 2: Light UI
(moved to installation manager frontend story)
Phase 3: Full-fledged application
The text was updated successfully, but these errors were encountered: