➜

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 loewis
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.11:45:23
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1366803923.93.0.189136886201.issue7475@psf.upfronthosting.co.za>
In-reply-to
Content 
I don't see any point in merely bringing the codecs back, without any convenience API to use them. If I need to do

  import codecs
  result = codecs.getencoder("base64").encode(data)

I don't think people would actually prefer this over

  import base64
  result = base64.encodebytes(data)

I't (IMO) only the convenience method (.encode) that made people love these codecs.
History
Date User Action Args
2013-04-24 11:45:24loewissetrecipients: + loewis, lemburg, gvanrossum, barry, georg.brandl, gregory.p.smith, jcea, cben, ncoghlan, belopolsky, vstinner, benjamin.peterson, ezio.melotti, eric.araujo, r.david.murray, ssbarnea, flox, petri.lehtinen, pconnell
2013-04-24 11:45:23loewissetmessageid: <1366803923.93.0.189136886201.issue7475@psf.upfronthosting.co.za>
2013-04-24 11:45:23loewislinkissue7475 messages
2013-04-24 11:45:23loewiscreate