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 Anthony.Kong, berker.peksag, catalin.iacob, eric.araujo, petri.lehtinen, pitrou, r.david.murray
Date 2012-02-16.21:14:32
SpamBayes Score 0.0017582733
Marked as misclassified No
Message-id <1329426873.44.0.0478894679015.issue13641@psf.upfronthosting.co.za>
In-reply-to
Content
Um.  I'm inclined to think that #13637 was a mistake.

Functions that accept bytes and return bytes and also accept string and return string seem uncontroversial.  However, accepting bytes or string and returning bytes is not an obviously good idea, and IMO at least merits some discussion.  In fact, I thought it *had* been discussed, specifically in the context of the b2a/a2b functions, and been rejected.
History
Date User Action Args
2012-02-16 21:14:33r.david.murraysetrecipients: + r.david.murray, pitrou, eric.araujo, catalin.iacob, petri.lehtinen, Anthony.Kong, berker.peksag
2012-02-16 21:14:33r.david.murraysetmessageid: <1329426873.44.0.0478894679015.issue13641@psf.upfronthosting.co.za>
2012-02-16 21:14:32r.david.murraylinkissue13641 messages
2012-02-16 21:14:32r.david.murraycreate