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 ezio.melotti
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:59:21
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1366721961.53.0.52000761101.issue7475@psf.upfronthosting.co.za>
In-reply-to
Content
While not strictly necessary, a PEP would be certainly useful and will help reaching a consensus.  The PEP should provide a summary of the available options (transform/untransforms, reintroducing encode/decode for bytes/str, maybe others), their intended behavior (e.g. is type(x.transform()) == type(x) always true?), and possible issues (e.g.  Should some transformations be limited to str or bytes?  Should rot13 work with both transform and untransform?).
Even if we all agreed on a solution, such document would still be useful IMHO.
History
Date User Action Args
2013-04-23 12:59:21ezio.melottisetrecipients: + ezio.melotti, lemburg, gvanrossum, loewis, barry, georg.brandl, jcea, cben, ncoghlan, belopolsky, vstinner, benjamin.peterson, eric.araujo, r.david.murray, ssbarnea, flox, petri.lehtinen, pconnell
2013-04-23 12:59:21ezio.melottisetmessageid: <1366721961.53.0.52000761101.issue7475@psf.upfronthosting.co.za>
2013-04-23 12:59:21ezio.melottilinkissue7475 messages
2013-04-23 12:59:21ezio.melotticreate