On Feb 28, 2006, at 1:35 PM, Russell E Owen wrote: > At 12:33 PM -0600 2006-02-28, Bob Ippolito wrote: >> On Feb 28, 2006, at 12:13 PM, Russell E. Owen wrote: >> >>> In article <[EMAIL PROTECTED]>, >>> Ronald Oussoren <[EMAIL PROTECTED]> wrote: >>> >>> ...you will have to make sure that /Library/Frameworks/ >>> Python.framework/Versions/2.4/bin >>> is at the start of your PATH. >>> >>> If you use bash[1] is you should create a .bash_profile file in >>> your >>> home directory that >>> contains the line PATH="/Library/Frameworks/Python.framework/ >>> Versions/ >>> 2.4/bin:$PATH". >>> >>> It seems unfortunate to put that long complicated mess into the >>> path, >>> and then have to redo it when python 2.5 comes out. >> >> The long way is the right way. Having to change your path when a >> new version of Python is installed is not a bad thing. > > OK, I'll do the long path. > > But I'm still puzzled about hard-coding the version. Why not just use: > > PATH="/Library/Frameworks/Python.framework/Versions/ > Current/bin:$PATH" > > and automatically get the current version? It seems to me that > would be best for most users and that experts who want finer > control would know what to do.
That's not necessarily a bad idea -bob _______________________________________________ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig
