Guido van Rossum wrote:
>>> c in string.whitespace --> c.isspace()
>>
>>This changes the meaning slightly for unicode characters, because
>>chr(i).isspace() != unichr(i).isspace()
>>for i in { 0x1c, 0x1d, 0x1e, 0x1f, 0x85, 0xa0 }
>
>
> That's unfortunate, because I'd like unicode to be an extension of
> ASCII also in this kind of functionality. What are these and why are
> they considered spaces? Would it hurt to make them spaces in ASCII
> too?
From the Unicode database:
001C;<control>;Cc;0;B;;;;;N;FILE SEPARATOR;;;;
001D;<control>;Cc;0;B;;;;;N;GROUP SEPARATOR;;;;
001E;<control>;Cc;0;B;;;;;N;RECORD SEPARATOR;;;;
001F;<control>;Cc;0;S;;;;;N;UNIT SEPARATOR;;;;
0085;<control>;Cc;0;B;;;;;N;NEXT LINE;;;;
00A0;NO-BREAK SPACE;Zs;0;CS;<noBreak> 0020;;;;N;NON-BREAKING SPACE;;;;
--
Marc-Andre Lemburg
CEO eGenix.com Software GmbH
______________________________________________________________________
Company & Consulting: http://www.egenix.com/
Python Software: http://www.egenix.com/files/python/
Meet us at EuroPython 2002: http://www.europython.org/
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4