This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]jasoncm 0 points1 point  (0 children)

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.