[Python-Dev] 2.3.5 schedule, and something I'd like to get in (original) (raw)
Ronald Oussoren ronaldoussoren at mac.com
Wed Jan 5 10:19:09 CET 2005
- Previous message: [Python-Dev] 2.3.5 schedule, and something I'd like to get in
- Next message: [Python-Dev] 2.3.5 schedule, and something I'd like to get in
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 5-jan-05, at 9:33, Martin v. Löwis wrote:
Bob Ippolito wrote:
It doesn't for reasons I care not to explain in depth, again. Search the pythonmac-sig archives for longer explanations. The gist is that you specifically do not want to link directly to the framework at all when building extensions. Because an Apple-built extension then may pick up a user-installed Python? Why can this problem not be solved by adding -F options, as Jack Jansen proposed?
It gets worse when you have a user-installed python 2.3 and a user-installed python 2.4. Those will be both be installed as /Library/Frameworks/Python.framework. This means that you cannot use the -F flag to select which one you want to link to, '-framework Python' will only link to the python that was installed the latest.
This is an issue on Mac OS X 10.2.
Ronald
- Previous message: [Python-Dev] 2.3.5 schedule, and something I'd like to get in
- Next message: [Python-Dev] 2.3.5 schedule, and something I'd like to get in
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]