Message147634
> But why are they not a space?
Because the Unicode standard says they are not. We have a good tradition in Python to follow standards where they apply, and it appears that the Unicode standard is crystal clear that the characters in question are *not* white space. Why should we second-guess the Unicode consortium when discussing Unicode questions? See also
http://en.wikipedia.org/wiki/Whitespace_character
IOW: get the Unicode consortium to declare them as whitespace, and we happily follow.
Ezio: I do think that _PyUnicode_IsWhitespace should use the White_Space property (from PropList.txt). I'm not quite sure how they computed that property (or whether it's manually curated). Since that's a behavioral change, it can only go into 3.3. |
|
Date |
User |
Action |
Args |
2011-11-14 21:33:07 | loewis | set | recipients:
+ loewis, ezio.melotti, mankyd |
2011-11-14 21:33:06 | loewis | set | messageid: <1321306387.0.0.638362418668.issue13391@psf.upfronthosting.co.za> |
2011-11-14 21:33:05 | loewis | link | issue13391 messages |
2011-11-14 21:33:05 | loewis | create | |
|