4 ms·
Yes, pip/virtualenv works for installing things like Django. It totally fails for something like m2sh which has to live in the system PATH so that you can run
by zedshaw 16y ago
Yes, pip/virtualenv works for installing things like Django.
It totally fails for something like m2sh which has to live in the system PATH so that you can run it from wherever you have your configs.
But you know, I wonder if the various distros could sort of invert this and they start using pip/virtualenv instead of everyone else working around them?
- jacobolus 16y agoThe distros should be shipping two versions of python (if they need), walling their required old version off somewhere but actively and explicitly including a newer one higher up in the $PATH so that people don’t have to mess with the “system”. The problem is the combination of “system”, “third-party tools”, and “users” trying to use the same python with completely different upgrade timelines. If all of these distros included by default a recent-ish version, and their package managers made updating that one a snap, then third-party tools could stop trying to use system python for anything at all, and users could forget that the “system” python existed. Unfortunately, since the problematic old python versions are on existing old distro versions, it’s not clear that there’s any easy way to fix this problem.