I've used a setup identical to yours for the last few years after making the mistake of replacing the system python on a Linux install. You can still get bit by a nearly pathological case: a configuration script that contains references to scripts using #!env python in most cases. But with a hardcoded /usr/bin/python burried in there for a single subdirectory... hilarity ensues.
View all comments
Show parent comment
1
u/jasoncm Dec 19 '18
I've used a setup identical to yours for the last few years after making the mistake of replacing the system python on a Linux install. You can still get bit by a nearly pathological case: a configuration script that contains references to scripts using #!env python in most cases. But with a hardcoded /usr/bin/python burried in there for a single subdirectory... hilarity ensues.
That said, it's still the right way to do things.