[Python-Dev] last second patches (was: regarding the Python Developer posting...)

[Tim Peters]

[M.-A. Lemburg, on /F's Unicode patches]
> Any chance of taking a look at it first ? (BTW, what happened to the
> usual post to SF, review, then checkin cycle ?)

I encouraged /F *not* to submit a patch for the unicodedatabase.c change.
He knows what he's doing, experts in an area are allowed (see PEP200) to
skip the patch business, and we're trying to make quick progress before
2.0b2 ships.

This change may be more controversial, though:

> The C type checks are a little performance sensitive since they
> are used on a char by char basis in the C implementation of
> .upper(), etc. -- do the new methods give the same performance ?

Don't know.  Although it's hard to imagine we have any Unicode apps out
there now that will notice one way or the other <wink>.