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 ezio.melotti
Recipients barry, belopolsky, benjamin.peterson, cben, eric.araujo, ezio.melotti, flox, georg.brandl, gregory.p.smith, gvanrossum, jcea, lemburg, loewis, ncoghlan, pconnell, petri.lehtinen, r.david.murray, ssbarnea, vstinner
Date 2013-04-24.12:20:46
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
IMHO it's also a documentation problem.  Once people figure out that they can't use encode/decode anymore, it's not immediately clear what they should do instead.  By reading the codecs docs[0] it's not obvious that it can be done with codecs.getencoder("...").encode/decode, so people waste time finding a solution, get annoyed, and blame Python 3 because it removed a simple way to use these codecs without making clear what should be used instead.
FWIW I don't care about having to do an extra import, but indeed something simpler than codecs.getencoder("...").encode/decode would be nice.

Date User Action Args
2013-04-24 12:20:46ezio.melottisetrecipients: + ezio.melotti, lemburg, gvanrossum, loewis, barry, georg.brandl, gregory.p.smith, jcea, cben, ncoghlan, belopolsky, vstinner, benjamin.peterson, eric.araujo, r.david.murray, ssbarnea, flox, petri.lehtinen, pconnell
2013-04-24 12:20:46ezio.melottisetmessageid: <>
2013-04-24 12:20:46ezio.melottilinkissue7475 messages
2013-04-24 12:20:46ezio.melotticreate