On Oct 09, 2010, at 02:48 AM, Stephen J. Turnbull wrote: >Right. That's where I was going with my comment to Barry about the >Received headers. Even if email isn't going to serve clients working >with wire format, it needs to deal with those headers. But where I >think the headers defined by RFC 822 should be stored as str in >email6, I am leaning toward storing Received headers verbatim as bytes >(including any RFC 822 folding whitespace) because of the RFC 5321 >requirement that they be preserved exactly.
I think then you'd have to have two different APIs. It'll just be too confusing and error prone to return either bytes or strs from header value accessors depending on the header name. -Barry
signature.asc
Description: PGP signature
_______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
