Charles just tried out the Enthought Python Distribution, which has a new and
different type of garbage:

PYTHON_LDLIBRARY = Python.framework/Versions/2.5.2001/Python

This trips up CIT_PYTHON_SYSCONFIG, which isn't expecting the ".2001".

There is a new wrinkle:  I just noticed that both our Macs have
/usr/lib/libpython2.3.dylib -- which, in turn, depends upon the framework.  This
leads me to believe that the simplistic code in the 'python2.x-config' utility
is the right way to do things.  Maybe one can pretend frameworks don't exist on
Mac OS X, and just use -lpython2.x.

Resolved: fixed on Cygwin (for both Cygwin Python and Python for Windows).

r5941 (cs/autoconf/trunk/cit_python.m4)

Fixed on Mac OS X.  (The Cygwin issue remains.)

r5301 (cs/autoconf/trunk/cit_python_sysconfig.m4)


Distutils seems to lack any facility for relinking the Python intepreter, which
means it is impossible to do embedding portably.  The fix above is another
special-case hack in a growing if-then-else ladder of such hacks.

Note that there is a third dicey platform: AIX.

On both platorms, try creating an extension module using pure distutils... if
that works, then clearly it knows something that my Autoconf macros don't.

This also doesn't work on Cygwin. "libpython2.4.dll.a" is nested inside Python's
'config' directory, where the linker can't find it.

I saw this before on Gurnis' Mac, and now it reproduces on my Mini... because I
upgraded to Tiger (?)

g++-3.3: Python.framework/Versions/2.3/Python: No such file or directory
m

PYTHON_LDLIBRARY is clearly broken: it's supposed to be "-framework Python" or
something.  But somehow I don't think it's my fault.  Is distutils broken on
Mac?  Whatever the case, need fix/work-around.