>That's probably because you use 2.6.4 when running interactively and the system python when using >FastScripts.
You hit the nail on the head. Printing sys.version resulted in 2.6.1. Wasn't expecting that, because I had updated previously on my other system and everything seemed to "just work." >Have you installed setuptools and pyobjc for python 2.6.4? The system ships with pyobjc, but that's >only for /usr/bin/python, not for the 2.6.4 you installed separately. I'm clearly not understanding how two different pythons work on one system. When I type "python" it "upgraded" to 2.6.4 for me. Off I go... (Maybe I should have just remained at 2.6.1 ....) -brainysmurf On Tue, Jan 5, 2010 at 7:46 PM, Ronald Oussoren <ronaldousso...@mac.com>wrote: > > On 5 Jan, 2010, at 11:54, Adam Morris wrote: > > > Hi all, > > > > Just trying to get my system set up for some coding ... decided to > reinstall everything (Snow Leopard) from scratch. What a mistake that was. > > > > I updated to 10.6.2, installed Xcode and THEN installed python 2.6.4. I > think that might have something to do with two problems I'm seeing. The > major one is: > > > > import Foundation, Appkit doesn't work with import error (copy of path is > is below) > > Have you installed setuptools and pyobjc for python 2.6.4? The system > ships with pyobjc, but that's only for /usr/bin/python, not for the 2.6.4 > you installed separately. > > > > > The other one -- I don't know if this is related -- but when I run in > interactive mode I can import appscripts no problemo but when I run it from > a script (with FastScripts) it gives me an import error. > > That's probably because you use 2.6.4 when running interactively and the > system python when using FastScripts. > > Ronald
_______________________________________________ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig
