[Pythonmac-SIG] PackMan issues
Just van Rossum
just at letterror.com
Tue Nov 4 04:11:23 EST 2003
Kevin Ollivier wrote:
> I've just posted a new release of wxPackMan at:
>
> http://www.theolliviers.com/python/wxpm
Two problems, the first is caused by bundlebuilder itself:
1)
With --semi-standalone, bundlebuilder uses the actual Python executable
path for the bootstrap #! line. Apparently this version was built on
Panther, so it uses #!/System/Library/Frameworks/...etc., which
obviously fails on Jaguar. (I tried to convince Jack back then that it
was better to just always use #!/usr/bin/python for bootstrapping
(--standalone already does this), I now wish I didn't give in...)
2)
After I fix the above problem manually, I get this error:
Traceback (most recent call last):
File
"/Volumes/TitaData/Users/just/Desktop/wxPackageManager.app/Contents/
Resources/wxPackageManager.py", line 32, in ?
from wxPython.wx import *
File
"/Library/Frameworks/Python.framework/Versions/2.3/lib/python2.3/site-
packages/PIL/__init__.py", line 20, in ?
ImportError: Failure linking new module: /usr/lib/libiconv.2.dylib:
dyld:
/Volumes/TitaData/Users/just/Desktop/wxPackageManager.app/Contents/MacOS
/wxPackageManager can't open library: /usr/lib/libiconv.2.dylib (No
such file or directory, errno = 2)
Maybe this is just proof that --semi-standalone apps built with
Panther's Python simply won't work on Jag, even if it has
Python.framework installed. Not sure what to suggest right now.
Just
More information about the Pythonmac-SIG
mailing list