Ezio Melotti added the comment:
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
----------
_______________________________________
Python tracker <[email protected]>
<http://bugs.python.org/issue7475>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
