canonical / canonical/layer-basic
Attempt to preserve system pip doesn't work
- Lingua principale
- Python
- Stelle
- 10
- Fork
- 42
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Descrizione
Currently, when not using a virtualenv, bootstrap_charm_deps() function saves a copy of /usr/bin/pip3, pip upgrades the system pip, and then restores the copy of /usr/bin/pip
This is presumably trying to undo the effect of pip-upgrading pip. But it does not achieve this, as the /usr/bin/pip3 file is just an entrypoint, that uses "from pip import main", and the pip upgrade is still in
/usr/local/lib/python3.5/dist-packages, and is used by the restored /usr/bin/pip3 just fine
pip3 needs pip uninstalling, as well as restoring /usr/bin/pip3, I think
Guida per i contributori
Nessuna guida per i contributori indicizzata per questo repository
Direzione di ricerca
Start at the bootstrap_charm_deps() entry point described in the issue and inspect how /usr/bin/pip3 is copied, upgraded, and restored. Verify the system pip installation under /usr/local/lib/python3.5/dist-packages is also handled, and consider the work complete when bootstrapping dependencies no longer leaves the upgraded system pip in use.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- python
- Ambito
- devops
- Tipo di issue
- Bug
- Difficoltà
- 3/5
- Tempo stimato
- 1-2 giorni
- Stato di attività
- Ferma
- Chiarezza
- Abbastanza chiara
- Idoneità per principianti
- 35/100