Re: email-6.0.0.a1

On 19/07/2011 22:21, R. David Murray wrote:
> The basic additional API is that a 'source' attribute contains the
> text the generator read from the input source, and a 'value' attribute
> that contains the value with all the Content-Transfer-Encoding stuff
> undone so that you have a real unicode string.  By changing a policy
> setting, you can have that value as the string value of the header.
> You can also assign a string with non-ASCII characters to a header, and
> the right thing will happen.  (Well, eventually it will happen...right
> now it only works correctly for unstructured headers).  Further, Date
> headers have a datetime attribute (and accept being set to a datetime),
> and address headers have attributes for accessing the individual addresses
> in the header.  Other structured headers will eventually grow additional
> attributes as well.

This all sounds pretty awesome, congrats :-)

Has the header wrapping bug that was all part of the big headers mess 
been resolved now?

cheers,

Chris

-- 
Simplistix - Content Management, Batch Processing & Python Consulting
             - http://www.simplistix.co.uk