[New-bugs-announce] [issue10587] Document the meaning of str methods
report at bugs.python.org
Tue Nov 30 06:46:46 CET 2010
New submission from Alexander Belopolsky <belopolsky at users.sourceforge.net>:
On Mon, Nov 29, 2010 at 4:13 PM, "Martin v. Löwis" <martin at v.loewis.de> 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
'ROMAN NUMERAL FIVE'
As far a I can tell, the source of Other_Alphabetic property data,
http://unicode.org/Public/UNIDATA/PropList.txt, is not even included in the unicodedata module and neither is SpecialCasing.txt which is necessary for implementing a compliant case mapping algorithm.
assignee: docs at python
nosy: belopolsky, docs at python
title: Document the meaning of str methods
versions: Python 3.2
Python tracker <report at bugs.python.org>
More information about the New-bugs-announce