Author ncoghlan
Recipients ncoghlan
Date 2013-04-25.07:40:50
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1366875650.57.0.151905786577.issue17840@psf.upfronthosting.co.za>
In-reply-to
Content
encodings.base64_codec currently uses "assert errors=='strict'" in a few places, since it doesn't actually support any of the Unicode specific error handling modes.

This should either be discarded entirely (and document that the error handling mode is irrelevant for this codec), or else turned into a real check that raises ValueError if an unsupported error mode is passed in.

I have a slight preference for just ignoring the error mode as irrelevant (since this isn't a text encoding in the normal Unicode serialisation-as-bytes sense).
History
Date User Action Args
2013-04-25 07:40:50ncoghlansetrecipients: + ncoghlan
2013-04-25 07:40:50ncoghlansetmessageid: <1366875650.57.0.151905786577.issue17840@psf.upfronthosting.co.za>
2013-04-25 07:40:50ncoghlanlinkissue17840 messages
2013-04-25 07:40:50ncoghlancreate