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 r.david.murray
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:42:27
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1366720947.48.0.171944614469.issue7475@psf.upfronthosting.co.za>
In-reply-to
Content
transform/untransform has approval-in-principle, adding encode/decode to the type that doesn't have them has been explicitly (and repeatedly :) rejected.

(I don't know about anybody else, but at this point I have written code that assumes that if an object has an 'encode' method, calling it will get me a bytes, and vice versa with 'decode'...an assumption I know is not "safe", but that I feel is useful duck typing in the contexts in which I used it.)

Nick wants a PEP, other people have said a PEP isn't necessary.  What is certainly necessary is for someone to pick up the ball and run with it.
History
Date User Action Args
2013-04-23 12:42:27r.david.murraysetrecipients: + r.david.murray, lemburg, gvanrossum, loewis, barry, georg.brandl, jcea, cben, ncoghlan, belopolsky, vstinner, benjamin.peterson, ezio.melotti, eric.araujo, ssbarnea, flox, petri.lehtinen, pconnell
2013-04-23 12:42:27r.david.murraysetmessageid: <1366720947.48.0.171944614469.issue7475@psf.upfronthosting.co.za>
2013-04-23 12:42:27r.david.murraylinkissue7475 messages
2013-04-23 12:42:27r.david.murraycreate