[Python-Dev] issue 9807 - a glitch in coexisting builds of different types (original) (raw)

Benjamin Peterson benjamin at python.org
Sat Oct 2 02:36:25 CEST 2010

2010/10/1 Barry Warsaw <barry at python.org>:

I can think of a couple of ways out, none of which are totally satisfying. Probably the easiest out is to change the PEP 3149 naming so that the files don't end in ".so".  E.g. use this instead:

 foo.cpython-32dmu-so  foo.cpython-32m-so

-1 Doesn't that break not only Python's convention for extensions on shared modules but also any *nix shared object?

or similar.  I think that'd be a fairly straightforward change, but it might break some useful assumptions (we'd still fall back to .so of course). Other ideas: - make import.c smarter so that you can match against other than just the  suffix.  probably a lot of work.

Although it would be more work, I think this is the most "correct" option.

-- Regards, Benjamin

More information about the Python-Dev mailing list