> > I added a symbolic "python2.3.5" in the directory "/usr/bin, > > pointing to the python program under 'Library/Frameworks/Python.framework", > > so I can invoke this python with the command "python2.3.5". > > Here's where you've deviated from the standard: As a rule, you shouldn't > out ANYTHING in /usr/bin. that's Apple's job. As you haven't written > over anything, it's probably not going to cause any problems, but the > usual solution is to add /usr/local/bin to your PATH instead, but adding > a line something like this to your
Yeah, yeah -- this is correct, Chris, and technically works, but doesn't *really* work on Mac OS X. Those of us who've come to Macs from UNIX are comfortable with it, but old-style Mac users (pre-2000) aren't used to PATH and hacking it, and their .login or .bashrc scripts tend to be odd barely-working mixtures of whatever other people have told them to put there. Once you've got a GUI, you can't go back. Read, my installers put links in /usr/bin/, too. It's really the only way to go, until Apple provides something like the Windows registry complete with a programmatic API for it. Bill _______________________________________________ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig
