Re: fixing the current email module

On Oct 8, 2009, at 11:43 AM, Stephen J. Turnbull wrote:

> I think the whole input format (note, not necessarily wire!) should be
> saved off on the top-level Message object (possibly in a file, per
> Barry's comments about that).  Subobjects could then refer to to
> pieces of that as position ranges.

I haven't made up my mind about that (it's been suggested before).   
The tricky thing will be keeping that cache in sync with any other  
model changes through the approved API.  IOW, if I overwrite a  
message's payload, that input format should probably be blown away.

> I have a feeling we should not try to decide what APIs we're going to
> spell as __str__ and __bytes__ yet.

Very good point.

-Barry