For #1, the change in flags makes sense.  Because Python 3.3 has flexible
string representations (PEP 393), the --with-wide-unicode configure flag has
gone away.  It's this flag that's represented by the 'u' in the .so file
name.

#2 is an unfortunate hack.  I had problems with this before.

I'm not sure what to do about these, but they are legitimate problems.
Probably the best thing to do is to remove the build flags from EXTENSION_TAG
and DBG_EXTENSION_TAG, and probably tagged_extname() needs to know whether
it's moving files for Python 3.3 or an earlier version.  I just took a cursory
look at the code but I think some refactoring is going to be necessary to
handle these problems.   I just don't have time right now to do that. :(

Attachment: signature.asc
Description: PGP signature

Reply via email to