In article <9b202abc1001051850o70d5262araf1e3fd84a168...@mail.gmail.com>, Adam Morris <amor...@mistermorris.com> wrote: > 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.
That's pretty much correct. However, Apple's Python isn't totally untouchable. It's fine to install additional packages to it; OS X thoughtfully comes installed with a setuptools easy_install in /usr/bin to make that easy. Additional site packages for it get installed into /Library/Python. What you shouldn't do is try to update the files in the python instance itself, which means anything in /System/Library/Frameworks/Python.frameworks or /usr/bin. And, as Ronald mentioned earlier, the Apple-supplied Python 2.6.1 on 10.6 comes with a version of PyObjC already installed. > 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. Unfortunately, it's not always that cut-and-dried. For instance, the current python.org installers are currently 32-bit only; the Apple-supplied Python 2.6 supports 64-bit as well. That's important for some users. -- Ned Deily, n...@acm.org _______________________________________________ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig
