[Email-SIG] Append behavior of __setitem__

[Barry Warsaw]

On Apr 11, 2009, at 5:17 PM, Tony Nelson wrote:

> Sure.  The header field should be parsed, if possible, and possibly  
> add a
> defect to the message.  For some header fields, the data should be  
> added to
> the previous Header instance; for others, an extra Header instance  
> might
> need to be created.

I don't follow this part.

> Message /generation/ should comply with what was in RFC 2822, where  
> this
> requirement was added, and also the new RFC 5322.

+1

-Barry

-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 304 bytes
Desc: This is a digitally signed message part
URL: <http://mail.python.org/pipermail/email-sig/attachments/20090413/5c20e644/attachment.pgp>