On Feb 22, 2005, at 18:06, Chris Barker wrote:
Bob Ippolito wrote:I also rarely screw with PATH. Using /usr/bin/env is saying "let PATH decide".
right. I am always working across platforms, so I want to specify which python to use, but not specify where to find it.
I use explicit paths like: # MacPython 2.3.5 /usr/local/bin/python2.3 # DarwinPorts Python 2.3.5 /opt/local/bin/python2.3
which are not going to work on my Linux box. I guess if you want to have two different python2.3.4s, you need to do this, however.
/usr/bin/env python2.3.5 is only going to work if Python 2.3.5 is already on your PATH. If you do not explicitly change your path, it will never be there, since /usr/local/bin, /opt/local/bin, etc. are not on the PATH by default.
-bob
_______________________________________________ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig
