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

2010-08-25 Thread R. David Murray
R. David Murray rdmur...@bitdance.com added the comment: Yes it does seem like it is too late for this, code might be depending on this behavior now in 2.7. -- nosy: +r.david.murray status: pending - closed ___ Python tracker rep...@bugs.python.org

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

2010-07-08 Thread Antoine Pitrou
Antoine Pitrou pit...@free.fr added the comment: It would be a change in behaviour, which is quite unacceptable for a bugfix release. I think this should be closed. -- nosy: +pitrou resolution: - rejected status: open - pending ___ Python tracker

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

2010-07-06 Thread Alexandre Vassalotti
Alexandre Vassalotti alexan...@peadrop.com added the comment: Closing this since Python 2.7 is out now. -- nosy: +alexandre.vassalotti resolution: - wont fix stage: needs patch - committed/rejected status: open - closed ___ Python tracker

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

2010-07-06 Thread Ezio Melotti
Ezio Melotti ezio.melo...@gmail.com added the comment: Isn't this a bug that could be fixed in 2.7.1? -- nosy: +ezio.melotti ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue2570 ___

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

2010-07-06 Thread Alexandre Vassalotti
Alexandre Vassalotti alexan...@peadrop.com added the comment: Actually, you are right. This could be added as bug fix. -- resolution: wont fix - stage: committed/rejected - needs patch status: closed - open ___ Python tracker rep...@bugs.python.org

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

2010-04-01 Thread Florent Xicluna
Changes by Florent Xicluna florent.xicl...@gmail.com: -- keywords: -26backport nosy: +benjamin.peterson, flox, pooryorick, zhirsch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue2570 ___

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

2009-03-28 Thread R. David Murray
Changes by R. David Murray rdmur...@bitdance.com: -- priority: - normal stage: - test needed type: - behavior versions: +Python 2.7 -Python 2.6 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue2570

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

2009-03-28 Thread R. David Murray
Changes by R. David Murray rdmur...@bitdance.com: -- keywords: +patch stage: test needed - needs patch Added file: http://bugs.python.org/file13450/issue2570-test.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue2570

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

2008-04-07 Thread Guido van Rossum
New submission from Guido van Rossum [EMAIL PROTECTED]: 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