3 ms·
I always have different python versions on system level (`$ sudo apt install python3.7 python3.8 python3.9 python3.10`) and use virtualenv to manage versions fo
by kh1 4y ago
I always have different python versions on system level (`$ sudo apt install python3.7 python3.8 python3.9 python3.10`) and use virtualenv to manage versions for each project (`$ virtualenv env -p python3.9`), and that has served me well for years. Could someone tell me why pyenv is superior?
- mpicker0 4y agopyenv can compile Python versions that might not be available with "apt install" yet. And you can have multiple minor versions available (3.7.8 and 3.7.9, for instance), if you ever need it.
- zach_garwood 4y agoI don't know if it's "superior", but it helps you manage / install / uninstall / set system Python versions, as well as virtualenv features. That's it.
- kh1 4y agoThanks. IMO changing system python versions might confuse some people. I often have to debug not-so-tech-savvy colleagues' python scripts/environments. If we used pyenv, I could picture me telling them that they forgot to switch system python environment.
- 0x008 4y agoIf you forget to activate the venv you cannot accidently install packages in your system python.