Author ncoghlan
Recipients eric.araujo, eric.smith, ncoghlan, pitrou, r.david.murray
Date 2010-09-29.21:55:56
SpamBayes Score 3.12612e-05
Marked as misclassified No
Message-id <1285797358.89.0.615919758335.issue9873@psf.upfronthosting.co.za>
In-reply-to
Content
One of Antoine's review comments made me realise I hadn't explicitly noted the "why not decode with latin-1?" rationale for the bytes handling. (It did come up in one or more of the myriad python-dev discussions on the topic, I just hadn't noted it here)

The primary reason for supporting ASCII compatible bytes directly is specifically to avoid the encoding and decoding overhead associated with the translation to unicode text. Making that overhead implicit rather than avoiding it altogether would be to quite miss the point of the API change.
History
Date User Action Args
2010-09-29 21:55:58ncoghlansetrecipients: + ncoghlan, pitrou, eric.smith, eric.araujo, r.david.murray
2010-09-29 21:55:58ncoghlansetmessageid: <1285797358.89.0.615919758335.issue9873@psf.upfronthosting.co.za>
2010-09-29 21:55:57ncoghlanlinkissue9873 messages
2010-09-29 21:55:56ncoghlancreate