[Python-Dev] Dropping bytes "support" in json
barry at python.org
Fri Apr 10 04:41:55 CEST 2009
On Apr 9, 2009, at 2:25 PM, Martin v. Löwis wrote:
>> This is an interesting question, and something I'm struggling with
>> the email package for 3.x. It turns out to be pretty convenient to
>> both a bytes and a string API, both for input and output, but I think
>> email really wants to be represented internally as bytes. Maybe. Or
>> maybe just for content bodies and not headers, or maybe both.
>> aside from that decision, I haven't come up with an elegant way to
>> /output/ in both bytes and strings (input is I think theoretically
>> easier by sniffing the arguments).
> If you allow for content-transfer-encoding: 8bit, I think there is
> no way to represent email as text. You have to accept conversion to,
> say, base64 (or quoted-unreadable) when converting an email message to
Agreed. But applications will want to deal with some parts of the
message as text on the boundaries. Internally, it should be all bytes
(although even that is a pain to write ;).
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 304 bytes
Desc: This is a digitally signed message part
More information about the Python-Dev