[New-bugs-announce] [issue2570] backport 3.0-style \u/\U processing in raw strings when unicode_literals is imported from __future__

[Guido van Rossum]

New submission from Guido van Rossum <guido at python.org>:

In 3.0, r'\u1234' is a string of 6 characters (\, u, 1, 2, 3, 4).  In
2.6, after "from __future__ import unicode_literals" it is a string of
one character (code point 0x1234).  IMO the 3.0 behavior should be
imported from the future as well (using the same import).

----------
components: Interpreter Core
keywords: 26backport
messages: 65090
nosy: gvanrossum
severity: normal
status: open
title: backport 3.0-style \u/\U processing in raw strings when unicode_literals is imported from __future__
versions: Python 2.6

__________________________________
Tracker <report at bugs.python.org>
<http://bugs.python.org/issue2570>
__________________________________