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 belopolsky
Recipients belopolsky, docs@python
Date 2010-11-30.05:46:44
SpamBayes Score 1.82905e-08
Marked as misclassified No
Message-id <>
On Mon, Nov 29, 2010 at 4:13 PM, "Martin v. Löwis" <> wrote:
>> - How specific should library reference manual be in defining methods
>> affected by UCD such as str.upper()?
> It should specify what this actually does in Unicode terminology
> (probably in addition to a layman's rephrase of that)

Some of the clarifications may actually lead to a conclusion that current behavior is wrong.  For example, Unicode defines Alphabetic property as Lu + Ll + Lt + Lm + Lo + Nl + Other_Alphabetic

However, str.isalpha() is defined as just Lu + Ll + Lt + Lm + Lo.  For example,

>>> import unicodedata as ud
>>> ud.category('Ⅴ')
>>> 'Ⅴ'.isalpha()

As far a I can tell, the source of Other_Alphabetic property data,, is not even included in the unicodedata module and neither is SpecialCasing.txt which is necessary for implementing a compliant case mapping algorithm.
Date User Action Args
2010-11-30 05:46:46belopolskysetrecipients: + belopolsky, docs@python
2010-11-30 05:46:46belopolskysetmessageid: <>
2010-11-30 05:46:44belopolskylinkissue10587 messages
2010-11-30 05:46:44belopolskycreate