This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author lemburg
Recipients
Date 2004-12-03.12:16:13
SpamBayes Score
Marked as misclassified
Message-id
In-reply-to
Content
Logged In: YES 
user_id=38388

Thanks for the patch. I see a few problems with this
approach, though:

* We brake binary compatibility depending on the configure
settings used for building Python; if this is really
necessary we should place the changes into the
_PyUnicode_ToLowerCase() et al. APIs defined in unicodectype.c

* I'm not sure whether there is any performance or memory
usage win in using the wctype functions from glibc: the
Unicode type mapping DB table has to be included anyway (due
to the title case mapping), so the only win I could see is a
performance one and given that towlower et al. do seem to be
locale aware I have strong doubts that these functions are
actually faster than the lookup in our own database.

Could you check whether using the wctype functions from
glibc does have any effect on size of the interpreter and
performance of e.g. .lower() and .upper() ?

If not, I'm inclined to remove the wctype function support
altogether.
History
Date User Action Args
2007-08-23 14:28:00adminlinkissue1076790 messages
2007-08-23 14:28:00admincreate