Message97035
Actually, I've already fixed this for 2.7 (issue 1680159) by letting the
UnicodeDecodeError propagate upward. I don't think making 'f' in u'foo'
an error would be a good idea.
Unless I'm mistaken the py3 behavior is correct. If someone has a case
where the py3 message or behavior is incorrect they can reopen (or open
a new issue, since the cause is likely to be different if there is a
problem).
(Actually, the message you get when you do 'o' in b'foo' is...not
obvious; but as I said I think that's a different issue from this one.) |
|
Date |
User |
Action |
Args |
2009-12-30 15:33:13 | r.david.murray | set | recipients:
+ r.david.murray, loewis, terry.reedy, ezio.melotti, mrabarnett |
2009-12-30 15:33:13 | r.david.murray | set | messageid: <1262187193.0.0.449402190912.issue4328@psf.upfronthosting.co.za> |
2009-12-30 15:33:10 | r.david.murray | link | issue4328 messages |
2009-12-30 15:33:10 | r.david.murray | create | |
|