This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author r.david.murray
Recipients ezio.melotti, loewis, mrabarnett, r.david.murray, terry.reedy
Date 2009-12-30.15:33:10
SpamBayes Score 0.00020825621
Marked as misclassified No
Message-id <1262187193.0.0.449402190912.issue4328@psf.upfronthosting.co.za>
In-reply-to
Content
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.)
History
Date User Action Args
2009-12-30 15:33:13r.david.murraysetrecipients: + r.david.murray, loewis, terry.reedy, ezio.melotti, mrabarnett
2009-12-30 15:33:13r.david.murraysetmessageid: <1262187193.0.0.449402190912.issue4328@psf.upfronthosting.co.za>
2009-12-30 15:33:10r.david.murraylinkissue4328 messages
2009-12-30 15:33:10r.david.murraycreate