[Email-SIG] Append behavior of __setitem__

[Tony Nelson]

At 10:04 -0400 04/13/2009, Barry Warsaw wrote:
 ...
>We could potentially have strict and lenient modes, or possible RFC
>822, 2822, 5322 modes.

Is there any need to produce emails that don't conform to the latest spec?
Those specs are crafted to produce backward-compatible messages.

>OTOH, I feel very strongly that the parser
>should accept just about any stream of bytes without throwing an
>exception.  Thinking about an application like Mailman, it's rather
>inconvenient for the parsing phase to throw any exception.  Much
>better is to register defects and then decide the disposition of
>messages based on the defect list.
>
>OTOH,

The second other hand should be the Gripping hand, as it should be the
overriding point.

>when creating messages from whole cloth, I think it's okay to
>raise exception.  You just have to be careful because often the same
>APIs are used by the parser.

APIs raise exceptions, parser catches them, makes into defects?
-- 
____________________________________________________________________
TonyN.:'                       <mailto:tonynelson at georgeanelson.com>
      '                              <http://www.georgeanelson.com/>