Comments on: PyObjc 2: Leopard, Python 2.5.1 and You.

By: jnoller

jnoller — Mon, 02 Feb 2009 05:24:35 +0000

See the comments above — the post by Anonymous worked, removing the altered path from .bash_profile worked great, the from the site version of python does not alter the framework version, in fact you can load it with /usr/bin/python

By: Erich Phillip

Erich Phillip — Mon, 02 Feb 2009 05:21:27 +0000

I did very much the same thing, and until I found your post, I was at a loss as to how to get around the PyObjC problem. Did you try using 'Pacifist' (http://www.charlessoft.com/) to reinstall PyObjC? I am going to try that, to see if I can restore Python, including PyObjC, to the state it comes in with Leopard. It is good to know, however, that if this does not fix my problem, I can try your solution.

I will let you know

By: jnoller

jnoller — Mon, 02 Feb 2009 00:24:35 +0000

See the comments above — the post by Anonymous worked, removing the altered path from .bash_profile worked great

By: Erich Phillip

Erich Phillip — Mon, 02 Feb 2009 00:21:27 +0000

By: Dewww

Dewww — Wed, 02 Jan 2008 20:14:27 +0000

I don’t know if this is a good thing or not, but I had installed Activestate python overtop of the /Library/Frameworks/Python.framework version and couldn’t import objc. After much nashing (as you say) I renamed /Library/Frameworks/Python.framework and started over with a sudo cp –Rp /System/Library/Frameworks/Python.framework /Library/Frameworks/Python.framework and now import objc works just fine, even import WebKit

By: Barry Wark

Barry Wark — Mon, 24 Dec 2007 19:43:53 +0000

Since I'm somewhat responsible for this fix, I should note that deleting thie "-isysroot /Developer/SDKs/MacOSX10.4u.sdk" line will have unforeseeable and potentially bad consequences down the road. Perhaps a better solution is to build the MacPython from source on Leopard so that it uses the 10.5 SDK. Although you'll have to rebuild all your extensions, this is probably the better way to go. There's a 10.5 SDK build available on my web site (http://rieke-server.physiol.washington.edu/~bar...). Give it a try, though I can't guarantee anything. It will install over the existing Python.framework (I don't know of any way around this since the python version is the same), so you should move your old one to somewhere safe before installing. You'll then have to re-install (and build) any modules and extensions that were installed in site-packages.

pyobjc2 will build and run just fine with this build.

By: jnoller

jnoller — Sat, 15 Dec 2007 00:33:15 +0000

Interesting, I may try this just to see if it will all work :)

By: Anonymous

Anonymous — Fri, 14 Dec 2007 23:20:43 +0000

The postflight script adds /Library/Frameworks/Python.framework/Versions/Current/bin to your PATH, but doesn't touch the system syslinks (at least not as far as I can tell). You can get rid of the python.org install just by removing/renaming the /Library/Frameworks/Python.framework directory, and optionally editing your .bash_profile to take the now-defunct directory out of your PATH.

By: David Reid

David Reid — Fri, 14 Dec 2007 22:09:11 +0000

They don't go to the same locations ... the original framework is still in /System/Library/Frameworks/Python.framework.

You'll want to go through /Library/Receipts/MacPython.mpkg and delete all the files referenced in the *.bom files

http://www.macworld.com/article/47341/2005/10/v...

I don't remember if the MacPython package uses any postflight scripts to set up symlinks and stuff like that though.

By: jnoller

jnoller — Fri, 14 Dec 2007 17:53:14 +0000

It’s not just un-install — it’s restoring to the original framework version that shipped w/ leopard