OK I've figured it out. After spending another morning doing a clean re-install (the do do do intro song is catchy the first time but lame after three... :)
To get PyObjC working on Python 2.6.4: Install Python 2.6.4 Install setuptools for 2.6.4 Install PyObjC using setuptools This process was not at all clear to me (even though instructions exist on the net in various places) because I hadn't internalized the idea that there is a (untouchable) system python as well as the latest version (which is clearly the one I want). That's where I need to direct my installs to. As for the debate about binaries, it seems to me that if there was better explanation of how to use Python effectively on the various operating systems, it would help a lot. Basically, install 2.6.4 and be done with it. The reason I've chosen Python is because I need the Natural Language Processing Toolkit and wasn't quite ready for the waters that awaited me in getting set up to code! (Maybe I should just post this somewhere more central?) -brainysmurf On Tue, Jan 5, 2010 at 1:12 PM, Ned Deily <n...@acm.org> wrote: > In article <49841e6f-aa0e-4e7b-bb1a-16170308f...@optonline.net>, > Charles Turner <vze26...@optonline.net> wrote: > > Also, given that both "pythons" in /usr/bin and /usr/local/bin are > > symlinks, you can rename these to suit your organizational requirements. > > Don't change the /usr/bin/python symlink or any other existing file in > /usr/bin! Anything there is part of OS X and managed by Apple. At > worst, you can break things on your system that depend on the > Apple-supplied Python and its packages. At best, your change will be > reverted by some future OS X system update. > > -- > Ned Deily, > n...@acm.org > > _______________________________________________ > Pythonmac-SIG maillist - Pythonmac-SIG@python.org > http://mail.python.org/mailman/listinfo/pythonmac-sig >
_______________________________________________ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig
