Details
-
Type:
RFC
-
Status: Adopted
-
Resolution: Unresolved
-
Component/s: DM
-
Labels:None
Description
I'd like to get a number of convenience packages installed (via conda) into our shared stacks:
- ginga
- ipywidgets
- ipyevents
- tqdm.
I'm not proposing that any of our code depend on them, and they're sufficiently for users to install on their own systems that we don't need to package them with eups.
The first three packages on the above list are dependencies of display_ginga, which provides a very convenient way to do image display directly within a remote notebook with no server setup or port forwarding. It's not yet polished enough that I'd recommend adding it to any of our metapackages, and once its dependencies are install it'll be very easy for users to just check out and set up from source.
The last package, tqdm, is a very nice progress bar widget that works well in notebooks, interactive Python prompts, and the command-line, and I'd found it very useful for interactive debugging and analysis tasks that nevertheless contain steps that involve some waiting.
Attachments
Issue Links
Activity
Also, such a list would be useful when Adam Thornton is configuring the JupyterLab system.
I think pipelines.lsst.io seems like a slightly better place for such a list than the Developer Guide, but I don't feel strongly about it. Any other opinions on where it goes?
Also, does anyone happen to know what should already go on such a list? I'm happy to put it together when implementing this RFC.
https://github.com/lsst-dm/shared-stack/blob/master/shared_stack.py#L99
(Pretty sure that pep8 & pyflakes are now in lsst_distrib, but they were't when that code was written.)
Since this is about shared stacks for developers and not distributed pipeline code, I think it must go into the Developer Guide. Another copy could go in the Pipelines docs as "you might find this useful" suggestions.
It doesn't seem that there are any objections. Main debate is where to document it.
Seems clear that it should be documented at https://developer.lsst.io/services/lsst-dev.html#lsst-dev-loadlsst, since that's the only place that we document shared stacks. If that gets too unwieldy, we could spin it out into another Developer Guide page.
We should maintain a documented list of such "courtesy-installed" packages so that we can be clear that they are available yet not to be used in any checked-in code.