Author ncoghlan
Recipients Dmitry.Jemerov, giampaolo.rodola, ncoghlan, pitrou, r.david.murray
Date 2010-09-19.20:54:14
SpamBayes Score 0.0160058
Marked as misclassified No
Message-id <1284929657.45.0.0473281470654.issue9360@psf.upfronthosting.co.za>
In-reply-to
Content
To make the distinction easier to remember, would it help if the methods that are currently set to return bytes instead accepted the typical encoding+errors parameters, with parallel *b APIs to get at the raw bytes?

My concern with the current API is that there isn't a clear indicator during normal programming as to which APIs return strings and which return the raw bytes and hence require further decoding.
History
Date User Action Args
2010-09-19 20:54:18ncoghlansetrecipients: + ncoghlan, pitrou, giampaolo.rodola, r.david.murray, Dmitry.Jemerov
2010-09-19 20:54:17ncoghlansetmessageid: <1284929657.45.0.0473281470654.issue9360@psf.upfronthosting.co.za>
2010-09-19 20:54:15ncoghlanlinkissue9360 messages
2010-09-19 20:54:14ncoghlancreate