This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ned.deily
Recipients Arfrever, Neurogeek, Ramchandra Apte, amaury.forgeotdarc, djc, doko, eric.araujo, ezio.melotti, jwilk, lemburg, loewis, ned.deily, neologix, petri.lehtinen, pitrou, python-dev, r.david.murray, rosslagerwall, rpetrov, vstinner
Date 2011-10-17.22:02:10
SpamBayes Score 1.1299423e-05
Marked as misclassified No
Message-id <1318888930.95.0.114302398963.issue12619@psf.upfronthosting.co.za>
In-reply-to
Content
What do you do for platforms like OS X where we support one set of binary files that contain multi-architecture C-files that can run as Intel-64, Intel-32 or PPC-32 on the same machine at user option at run time?  For example, the Apple-suppled system Python on OS X 10.6 has all three and you can use `arch` to specify which to run (PPC is emulated on the Intel machines supported by 10.6):

$ file /usr/bin/python2.6
/usr/bin/python2.6: Mach-O universal binary with 3 architectures
/usr/bin/python2.6 (for architecture x86_64):	Mach-O 64-bit executable x86_64
/usr/bin/python2.6 (for architecture i386):	Mach-O executable i386
/usr/bin/python2.6 (for architecture ppc7400):	Mach-O executable ppc

The static IN.py currently shipped in plat-darwin is misleading at best. And you can't improve the situation by regenerating at installation time.
History
Date User Action Args
2011-10-17 22:02:11ned.deilysetrecipients: + ned.deily, lemburg, loewis, doko, amaury.forgeotdarc, pitrou, vstinner, jwilk, djc, ezio.melotti, eric.araujo, rpetrov, Arfrever, r.david.murray, Neurogeek, neologix, rosslagerwall, python-dev, petri.lehtinen, Ramchandra Apte
2011-10-17 22:02:10ned.deilysetmessageid: <1318888930.95.0.114302398963.issue12619@psf.upfronthosting.co.za>
2011-10-17 22:02:10ned.deilylinkissue12619 messages
2011-10-17 22:02:10ned.deilycreate