Created on 2011-02-16 23:29 by haypo, last changed 2011-02-16 23:57 by haypo. This issue is now closed.
| Messages (3) | |||
|---|---|---|---|
| msg128701 - (view) | Author: STINNER Victor (haypo) *  |
Date: 2011-02-16 23:29 | |
len(ur'\u0000') == len(u'\u0000') == 1 len(ur'\U0010FFFF') == len(u'\U0010FFFF') == 1 but >>> len(ur'\n'), len(u'\n') (2, 1) >>> len(ur'\x00'), len(u'\x00') (4, 1) \u and \U should not be interpreted in raw Unicode strings. |
|||
| msg128703 - (view) | Author: Amaury Forgeot d'Arc (amaury.forgeotdarc) * |
Date: 2011-02-16 23:55 | |
This has changed in python 3, and is even documented: http://docs.python.org/dev/py3k/whatsnew/3.0.html#text-vs-data-instead-of-unicode-vs-8-bit (6th bullet) Python 2.x could not be changed, for compatibility reasons. |
|||
| msg128704 - (view) | Author: STINNER Victor (haypo) * |
Date: 2011-02-16 23:57 | |
> Python 2.x could not be changed, for compatibility reasons. Well, it is not a bug because it is documented! << When an 'r' or 'R' prefix is used in conjunction with a 'u' or 'U' prefix, then the \uXXXX and \UXXXXXXXX escape sequences are processed while all other backslashes are left in the string. >> I agree that Python2 cannot be changed, but this behaviour is a little bit surprising :-) Let's move to Python3! |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2011-02-16 23:57:01 | haypo | set | status: open -> closed messages: + msg128704 resolution: invalid |
| 2011-02-16 23:55:18 | amaury.forgeotdarc | set | nosy:
+ amaury.forgeotdarc messages: + msg128703 |
| 2011-02-16 23:29:25 | haypo | create | |