[Pythonmac-SIG] Re: PIL 1.1.4 breaks Python 2.3 on Mac OS X 10.3 Panther

Alexandre Parenteau aparente at adobe.com
Fri Oct 31 19:24:53 EST 2003


> Thanks to some kind folks on the MacPython ichat channel last night,
> we tracked the problem down further.  The build process is for some
> reason creating an _imaging.so file with the following names in it:
> % otool -Lv /Library/Python/2.3/PIL/_imaging.so
> /Library/Python/2.3/PIL/_imaging.so:
> Python.framework/Versions/2.3/Python (compatibility version 2.3.0, current
> version 2.3.0)
> time stamp 1067389093 Tue Oct 28 16:58:13 2003
> /usr/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.0.0)
> time stamp 1064385339 Tue Sep 23 23:35:39 2003
> /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version
> 71.0.0)
> time stamp 1064354548 Tue Sep 23 15:02:28 2003
> %
> For some reason, the first line "Python.framework..." is wrong (don't
> ask me how I know -- I was told).  By applying another magic
> incantation,

If you link a python module using 'Python.framework/Versions/2.3/Python', it
means that the Python framework is going to be searched inside (in order):


So if you compile PIL, and then launch it on a machine which has a Python
inside both /Library, and /System/Library, then you'd better use
/usr/local/bin/python, else /usr/bin/python is going to load
/System/Library/Frameworks/Python, but the python module is going to load

Jack, what are the guidelines for linking a Python module ? I see Apple's
Panther Python is using
/System/Library/Frameworks/Python.framework/Versions/2.3/Python. And you
seem to be using /Library/Frameworks/Python.framework/Versions/2.3/Python.

This should work (I think), but do we need to be that explicit ? Shouldn't
'Python.framework/Versions/2.3/Python' be better so the extension can be
used in both Frameworks (?).

The mystery of Python loading...


> % install_name_tool -change Python.framework/Versions/2.3/Python \
>   /System/Library/Frameworks/Python.framework/Versions/2.3/Python
> things get fixed, and the Image module loads properly.
> It seems to me that this means there's a bug somewhere in gcc 3.3 as
> deployed on MacOS 10.3.  Something's putting that bad name in there.
> Bill
> _______________________________________________
> Pythonmac-SIG maillist  -  Pythonmac-SIG at python.org
> http://mail.python.org/mailman/listinfo/pythonmac-sig

Alexandre Parenteau
Computer Scientist
Core Technologies, AGM
Adobe Systems, Inc.

More information about the Pythonmac-SIG mailing list