Thanks! I've always used pip and never had issues with it so I couldn't understand why use another package manager. But if at some point I find some issue I know where to look for ;)
It's not "another package manager", it's a separate build and packaging system. E.g., you can use conda for non-Python stuff like C binaries and libraries, or R packages. Where it shines generally is in being able to ship binary CPython/C extensions and libraries that are magically rpathed upon install so there's no building happening on the client host and things are just getting installed and work right off the bat.
You can also install conda without admin rights. I can highly recommend it - install conda (miniconda is probably best here) and then create a new environment. You can keep it all local without sudo/admin rights!
That will only isolate Python packages. The binary you run is still the one installed system-wide. The alternative is really pyenv, or compiling Python yourself.
He says that there are many codes running in the background that would have to be changed.. my best guess is it'll stay like that until the server dies. Can't go with venv too, since he doesn't wanna deal with it neither
Installing Python 3 at the system level doesn't affect Python 2, or any of the legacy code. Python 2's executable is (usually) python, and Python 3 is python3, so you can have both installed along side each other.
Also, look into environment modules for providing and loading different software at different versions.
144
u/[deleted] Oct 05 '20
Aaand here I'm stuck with 2.7 because root user doesn't want to deal with updating it, I can't even use keras