On Sat, Oct 2, 2010 at 10:36 AM, Benjamin Peterson <benja...@python.org> wrote: > 2010/10/1 Barry Warsaw <ba...@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.
I agree with Benjamin here - making import.c handle the situation properly seems like a much better option (and import.c isn't *quite* as ugly as it was before Victor started cleaning it up to handle Unicode paths properly). Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
