[Python-Dev] Problem with module loading on multi-arch? (original) (raw)
Thomas Wouters thomas at python.org
Sat Mar 18 02:45:21 CET 2006
- Previous message: [Python-Dev] Problem with module loading on multi-arch?
- Next message: [Python-Dev] Problem with module loading on multi-arch?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 3/18/06, Neal Becker <ndbecker2 at gmail.com> wrote:
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.
Not within a single interpreter, I'd say. Extensions compiled for x86_64 will not load into an interpreter compiled for x86, and vice-versa, so that's out of the question. What else should python support? You can, of course, have different interpreters live next to each other -- python already supports that just fine. Python shouldn't care about architectures, though, and just use 'prefix' and 'exec_prefix' as they were given at compiletime; they contain the properly compiled extensions for that interpreter. For the purpose of multi-archedness, python and all its modules and extensions are a single application.
Perhaps Py3K should differentiate more between .so files and .py files (and .pyc/.pyo files), but I'm not entirely convinced of the value of installing a module once for multiple interpreters.
-- Thomas Wouters <thomas at python.org>
Hi! I'm a .signature virus! copy me into your .signature file to help me spread! -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.python.org/pipermail/python-dev/attachments/20060318/e8102c1f/attachment.html
- Previous message: [Python-Dev] Problem with module loading on multi-arch?
- Next message: [Python-Dev] Problem with module loading on multi-arch?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]