I have the same issue when creating a new PyObjC project. Moving Python.framework outside of my /Library/Frameworks folder "fixes" it, but as LaskoVortex pointed out, this is no good if you actually intend to distribute your app.
I have found a simple fix, though. As far as I can tell, the version of Python 2.5 installed by MacPython has no problem running the PyObjC module. The problem is that the PyObjC modules are in the
other version of the framework (the one in /System/Library/Frameworks), and the MacPython version isn't aware of them. So we need to add the path to these modules to the "PYTHONPATH" environment variable.
So here's the fix:
In your XCode project, open the "main.m" file (
not "main.py"). Near the beginning of the file, you should see:
Code:
int main(int argc, char *argv[])
{
[INDENT]
NSAutoreleasePool *pool = [[NSAutoreleasePool alloc] init];
NSBundle *mainBundle = [NSBundle mainBundle];
NSString *resourcePath = [mainBundle resourcePath];
NSArray *pythonPathArray = [NSArray arrayWithObjects: resourcePath, [resourcePath stringByAppendingPathComponent:@"PyObjC"], nil];
setenv("PYTHONPATH", [[pythonPathArray componentsJoinedByString:@":"] UTF8String], 1);
[/INDENT]
...
Replace this line:
Code:
NSArray *pythonPathArray = [NSArray arrayWithObjects: resourcePath, [resourcePath stringByAppendingPathComponent:@"PyObjC"], nil];
with this:
Code:
NSArray *pythonPathArray = [NSArray arrayWithObjects: resourcePath, [resourcePath stringByAppendingPathComponent:@"PyObjC"], @"/System/Library/Frameworks/Python.framework/Versions/Current/Extras/lib/python/", nil];
And that's it. Build and run the project.
Note: I have not tested this very thoroughly but it works with the basic tests I've done. If you use it in your own code, make sure to test everything thoroughly to make sure it works.
This fix should make your project work regardless of whether MacPython is installed. If MacPython
is installed, your app will run using the version of Python installed by MacPython. So if that version is older than 2.5, it may not be able to load the objc module (I haven't tested this). Even so, this is way better than not working if
any version of MacPython is installed.
This workaround notwithstanding, Apple really needs to fix this behavior. At the very least, they could do what I've described here. But ideally, they should make PyObjC apps
only use the "System" version of the Python framework.
. Could I just uninstall it, since os x 10.5 comes with 2.5?