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.15:02:13
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1366729333.32.0.406752137934.issue7475@psf.upfronthosting.co.za>
In-reply-to
Content
I agree with you.  transform/untransform are parallel to encode/decode, and I wouldn't expect them to exist on any type that didn't support either encode or decode.  They are convenience methods, just as encode/decode are.

I am also probably not invested enough in it to write the PEP :)
History
Date User Action Args
2013-04-23 15:02:13r.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 15:02:13r.david.murraysetmessageid: <1366729333.32.0.406752137934.issue7475@psf.upfronthosting.co.za>
2013-04-23 15:02:13r.david.murraylinkissue7475 messages
2013-04-23 15:02:13r.david.murraycreate