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 andersch, lemburg, loewis
Date 2009-03-21.09:40:07
SpamBayes Score 4.858313e-07
Marked as misclassified No
Message-id <1237628409.49.0.0191517288557.issue1498930@psf.upfronthosting.co.za>
In-reply-to
Content
You may not know it, but these functions are generated from the Unicode
database. 

However, because these functions need to be fast and are small enough,
they were not converted to the unicodetype_db approach and instead left
as they were originally implemented: as switch statements for the
compilers to optimize.

Is there any reason why this would need to change for Unicode 5.0 ?
History
Date User Action Args
2009-03-21 09:40:09lemburgsetrecipients: + lemburg, loewis, andersch
2009-03-21 09:40:09lemburgsetmessageid: <1237628409.49.0.0191517288557.issue1498930@psf.upfronthosting.co.za>
2009-03-21 09:40:08lemburglinkissue1498930 messages
2009-03-21 09:40:07lemburgcreate