A RetroSearch Logo

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

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2006-September/068816.html below:

[Python-Dev] python, lipo and the future?

[Python-Dev] python, lipo and the future? [Python-Dev] python, lipo and the future?"Martin v. Löwis" martin at v.loewis.de
Sun Sep 17 22:27:42 CEST 2006
Jack Jansen schrieb:
> Just wondering: is it a good idea in the first place to create a  
> universal 32/64 bit Python on MacOSX?

I wonder about the same thing.

> For extension modules it's different, though: there it would be nice  
> to be able to have a single module that could load into any Python  
> (32/64 bit, Intel/PPC) on any applicable MacOSX version.

That seems to suggest that the standard distribution should indeed
provide a four-times fat binary, at least for libpython: AFAIU,
to build extension modules that way, all target architectures must
be supported in all necessary libraries on the build machine (somebody
will surely correct me if that's wrong).

Regards,
Martin
More information about the Python-Dev mailing list

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