4 ms·
What if your package manager doesn't support the version of Python you're targeting? The most common place this happens is if you have some old RHEL 5 boxen th
by j_baker 15y ago
What if your package manager doesn't support the version of Python you're targeting? The most common place this happens is if you have some old RHEL 5 boxen that haven't been upgraded (and who that uses RHEL doesn't?). Or suppose you use python 2.7, which isn't supported by very many (any?) "stable" linuces (aka Debian stable, RHEL, Ubuntu LTR, etc).
And installing packages into the system python (if that's what you're suggesting) is the path to madness. It's much better to use virtualenvs you can throw away at will. All in all, it's usually best just to leave the system Python alone to avoid causing problems with any other packages that may depend on it being in a consistent state.
- mindrunner 15y agoThis problem really echoed with me. The one thing I hate about Python is the pain of compiling it from source. Unlike startups, we enterprise dudes don't have the liberty of choosing the latest distros with better base Python versions.in some cases,the machines don't even have a compiler installed. Try running your funky new admin script on these rhel5 boxen is a pain. I've resorted to compiling with LD_RUN_PATH, -rpath & -r set. I think this should be included in the python-guide for the sanity of other devops dudes