[Pythonmac-SIG] PackMan issues
kevino at tulane.edu
Sun Nov 2 16:18:08 EST 2003
On Nov 2, 2003, at 12:11 PM, Bob Ippolito wrote:
> On Nov 2, 2003, at 2:54 PM, Kevin Ollivier wrote:
>>> 2) it doesn't work w/o Jack's MacPython installed because you put
>>> #!/usr/local/bin/python in the bootstrap script
>> Since wxPython is compiled with gcc 3.1, it wouldn't work without
>> MacPython anyways. ;-) I hope to have this issue resolved soon, but
>> in the meantime it needs to run from Jack's installation.
> That's not true, Python extensions do not use the C++ ABI. It works
> just fine on Panther if you use #!/usr/bin/env python. It doesn't
> matter which compiler you used, because it's only using C to link the
True, but isn't that because the Python binary in the app bundle is
linked to the Python Framework? The hashbang script just sets a few env
variables and calls Contents/MacOS/python, which is linked to the
MacPython framework build. That's why even if you use #!/usr/bin/env
python, the installed status of packages tells whether or not the
package is installed in the Framework build, not if they are installed
I don't yet know the exact reason why wxPython is failing when run from
/usr/bin/python, but it is failing. If I use /usr/bin/python on Panther
instead to build the bundlebuilder app, and then copy in the wxPython
module, it crashes on load. I get the same result (gives a 'bus error'
message) if I copy the wxPython module into /Library/Python/2.3 and try
to use /usr/bin/pythonw to run a wxPython script. This same wxPython
module works fine with the Framework build of Python.
I could well be misunderstanding something here, and if so please let
me know, but there is something that is causing wxPython to fail with
Apple's Python build. I simply thought a recompile would be the most
likely way to resolve the issue.
More information about the Pythonmac-SIG