Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2000-October/009677.html below:

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

• Previous message: [Python-Dev] Patch to avoid conflict with older versions of Python.
• Next message: [Python-Dev] What is --with-next-framework
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

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.

=46rom 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?

Regards,
Martin

• Previous message: [Python-Dev] Patch to avoid conflict with older versions of Python.
• Next message: [Python-Dev] What is --with-next-framework
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4