[Python-Dev] What is --with-next-framework

[Guido van Rossum]

> I've been trying to understand how --with-next-framework is supposed
> to work, and on what systems it is supposed to work - with little
> success.
> 
> From what I understand, it will create a python2.0.dylib, and it will
> pass that to the linker when linking extension modules. Fine.
> 
> What confuses me is the snippet in Modules/getpath.c, where it somehow
> assumes that the Python library will live in an unversioned lib
> directory relative to the location of the Python framework. How is
> that supposed to work? Is anybody here willing to claim that this code
> is not entirely broken?

It's most likely broken.  Which suggests that nobody has tried it in a
*looooooong* time.  I have no idea what the --with-next-framework
option does, and I have no idea what a NeXT framework is.

Why are we still trying to support NeXT?  Isn't it completely
obsolete?

I propose to rip out --with-next-framework and be done with it.  If
you feel --with-next-framework is worth having, feel free to propose
platform-specific fixes to getpathp.c.

--Guido van Rossum (home page: http://www.python.org/~guido/)