[Python-Dev] issue 9807 - a glitch in coexisting builds of different types
barry at python.org
Mon Oct 4 20:43:35 CEST 2010
On Oct 01, 2010, at 07:36 PM, Benjamin Peterson wrote:
>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:
>-1 Doesn't that break not only Python's convention for extensions on
>shared modules but also any *nix shared object?
It shouldn't (i.e. if -Wl,-h is used to get the soname compiled in there), but
still I don't like it, and now I know it's not necessary.
>> 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"
Phew! Extra work averted! (see my other reply :).
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 836 bytes
Desc: not available
More information about the Python-Dev