Author flox
Recipients barry, belopolsky, benjamin.peterson, cben, eric.araujo, ezio.melotti, flox, georg.brandl, gvanrossum, jcea, lemburg, loewis, ncoghlan, pconnell, petri.lehtinen, r.david.murray, ssbarnea, vstinner
Date 2013-04-23.12:54:03
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1366721644.3.0.727646834547.issue7475@psf.upfronthosting.co.za>
In-reply-to
Content
I am not a native english speaker, but it seems that the common usage of encode/decode is wider than the restricted definition applied for Python 3.3:

Some examples:

* RFC 4648 specifies "Base16, Base32, and Base64 Data Encodings"
  http://tools.ietf.org/html/rfc4648

* About rot13: "the same code can be used for encoding and decoding"
  http://www.catb.org/~esr/jargon/html/R/rot13.html

* The Huffman coding is "an entropy encoding algorithm" (used for DEFLATE)
  http://en.wikipedia.org/wiki/Huffman_coding

* RFC 2616 lists (zlib's) deflate or gzip as "encoding transformations"
  http://tools.ietf.org/html/rfc2616#section-3.5


However, I acknowledge that there are valid reasons to choose a different verb too.
History
Date User Action Args
2013-04-23 12:54:04floxsetrecipients: + flox, lemburg, gvanrossum, loewis, barry, georg.brandl, jcea, cben, ncoghlan, belopolsky, vstinner, benjamin.peterson, ezio.melotti, eric.araujo, r.david.murray, ssbarnea, petri.lehtinen, pconnell
2013-04-23 12:54:04floxsetmessageid: <1366721644.3.0.727646834547.issue7475@psf.upfronthosting.co.za>
2013-04-23 12:54:04floxlinkissue7475 messages
2013-04-23 12:54:03floxcreate