[Python-Dev] Problem with module loading on multi-arch? (original) (raw)

Bob Ippolito bob at redivi.com
Sat Mar 18 02:52:22 CET 2006

On Mar 17, 2006, at 4:38 PM, Neal Becker wrote:

"Martin v. Löwis" wrote:

Neal Becker wrote: Sorry, maybe I used confusing terminology.

A reference is here: http://fedoraproject.org/wiki/Packaging/Python This is the current setup. For example, this is a standard macro used by Redhat in RPM SPEC files for python: _%define pythonsitearch %(%{python} -c "from distutils.sysconfig import getpythonlib; print getpythonlib(1)")} _%define pythonsitelib %(%{python} -c "from distutils.sysconfig import getpythonlib; print getpythonlib()")} Clearly this practice is widespread. It would seem that module search needs some modification to fully support it. Ah. That isn't supported at all, at the moment. Redhat should not be using it. Instead, there shouldn't be a difference between sitearch and sitelib. x8664 is multiarch. That means, we allow both i386 and x8664 binaries to coexits. Is the proposal that python should not support this? That would be unfortunate. I suspect is would not be that difficult to correctly support multiarch platforms. As it is, this usually works - but the example I gave above shows where it seems to break.

All the difficult issues supporting multi-arch are going to be with
distutils, not Python itself.

On OS X it isn't all that hard to support (beyond backwards
compatibility issues) because you run gcc once with the right options
and get a single universal binary as output. It would be a lot more
invasive if GCC had to be run multiple times and the products had to
be put in different places.

-bob

More information about the Python-Dev mailing list