Done
Pinned fields
Click on the next to a field label to start pinning.
Details
Details
Assignee
Brian Van Klaveren
Brian Van KlaverenReporter
Brian Van Klaveren
Brian Van KlaverenReviewers
Gabriele Comoretto [X]
Kian-Tat Lim
RubinTeam
Architecture
Components
Checklist
Checklist
Created May 18, 2020 at 7:23 PM
Updated June 19, 2020 at 1:28 AM
Resolved June 5, 2020 at 5:40 PM
Using
conda env export
is susceptible to not being resolvable if a package is marked as broken. We should switch to usingconda list --explicit
to avoid this issue.This triggers a few different modifications:
1. newinstall/lsstsw need to be modified to install using conda install. This is a different workflow than the existing workflow.
2. newinstall/lsstsw should probably be backwards compatible with previous methods
3. pip packages should be moved into conda-forge (pytest-subtests, peigen) as conda list --explicit does not seem to spit out packages installed by pip
4. Some additional work with the conda-forge team is necessary to ensure broken packages are NOT removed for the CDN the way the currently are, but are removed from the metadata. This ensure broken packages are still installable