Message187696
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.
[0]: http://docs.python.org/3/library/codecs.html |
|
Date |
User |
Action |
Args |
2013-04-24 12:20:46 | ezio.melotti | set | recipients:
+ 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:46 | ezio.melotti | set | messageid: <1366806046.83.0.51376866392.issue7475@psf.upfronthosting.co.za> |
2013-04-24 12:20:46 | ezio.melotti | link | issue7475 messages |
2013-04-24 12:20:46 | ezio.melotti | create | |
|