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 SilentGhost, ezio.melotti, lemburg, loewis, r.david.murray, serhiy.storchaka, spaceone, vstinner
Date 2015-12-18.19:25:11
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1450466711.68.0.954133179302.issue25880@psf.upfronthosting.co.za>
In-reply-to
Content
I wonder if we originally only had UnicodeError and it got split later but these codecs were never updated.  The codecs date back to the start of unicode support in python2, I think.

Adding MAL, he's likely to have an opinion on this ;)

Oh, right.  The more likely possibility is that there was (in python2) no way to know if the operation was (from the user's POV) encoding or decoding when the codec was called.  In python3 we do know, when the codec is called via encode/decode, but the codecs are still generic in principle.  So yeah, we need MAL's opinion.  (Or, I could be completely confused, since I always found encode/decode confusing in python2 :)
History
Date User Action Args
2015-12-18 19:25:11r.david.murraysetrecipients: + r.david.murray, lemburg, loewis, vstinner, ezio.melotti, SilentGhost, serhiy.storchaka, spaceone
2015-12-18 19:25:11r.david.murraysetmessageid: <1450466711.68.0.954133179302.issue25880@psf.upfronthosting.co.za>
2015-12-18 19:25:11r.david.murraylinkissue25880 messages
2015-12-18 19:25:11r.david.murraycreate