[issue5447] future unicode literals and r'\u'

Changes by Florent Xicluna : -- superseder: -> backport 3.0-style \u/\U processing in raw strings when unicode_literals is imported from __future__ ___ Python tracker ___ __

[issue5447] future unicode literals and r'\u'

Florent Xicluna added the comment: Duplicate of #2570. -- nosy: +flox resolution: -> duplicate status: open -> closed ___ Python tracker ___

[issue5447] future unicode literals and r'\u'

Zach Hirsch added the comment: I've hit this, too, and it's annoyed me. So here's a patch against trunk that should fix it. The idea is: whenever unicode_literals are turned on (or the -U command line flag is passed), to convert r"\u" to "\u005c\u0075" and r"\U" to "\u005c\u0055" for every str

[issue5447] future unicode literals and r'\u'

Benjamin Peterson added the comment: This happens with unicode literals even without "from __future__ import unicode_literals" because raw strings still have \u escapes interpreted. This isn't true in 3.0, so it would be nice to disable it with unicode_literals. -- message_count: 1.0 ->

[issue5447] future unicode literals and r'\u'

New submission from Poor Yorick : from __future__ import unicode_literals print(r'\u.bug') SyntaxError: (unicode error) truncated \u -- components: Interpreter Core message_count: 1.0 messages: 83326 nosy: pooryorick nosy_count: 1.0 severity: normal status: open title: future unicod