At 16:41 -0500 2009/03/30, Barry Warsaw wrote:
>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>On Mar 30, 2009, at 3:10 PM, Tony Nelson wrote:
>
>>I'm Tony Nelson. ...
 ...

>Hi Tony, welcome to the email sig!

Thank you.

>I'm actually sprinting on the
>email package today at Pycon.  Chris Withers joined me until he had to
>fly home.  Bug 1974 was Chris's particular itch and I now think I have
>a fix for this that isn't horrible, though unfortunately it will only
>land in 2.7 and shouldn't be back ported.

A worthy issue.  Hopefully header parsing and generation can be cleaned up
more befre 2.7/3.1 so that proper RFC2822 2.2.3 folding can be the norm.
For example, unstructured header fields such as Subject: have whitespace as
part of the unstructured token, and structured fields can skip whitespace,
so leading whitespace should not be stripped by
FeedParser._parse_headers().  This would help with idempotency.


>>Currently I've filed "[issue5610] email feedparser.py CRLFLF bug: $ vs
>>\Z". ...
 ...
>> I might be persuaded to review or fix other open issues.
>
>Very cool, thanks.  I'll look at the above issues after I land the
>patch for 1974.

Ack.  Only one issue yet [issue5610]; I want to know if I'm doing it right
before filing others.


>My plan for the email package is:
>
>* Fix what we can for Python 2.7 but be very conservative with back
>ports to 2.6
>* Ignore 3.0
>* Work on a new API so that we can actually fix the horrible
>brokenness of email in Python 3.

Hmm, I haven't used Python 3 yet, and didn't know about that.  I suppose it
is due to bytes/unicode confusion?

There should be an "obvious" place for users to get a current email package
suitable for at least the last few Python 2.x, at least if it starts
getting more love again.  I don't know quite where that should be, whether
a SourceForge (or similar) page, a listing on PyPI, both, or what.  Just
something simpler than a SVN checkout.
-- 
____________________________________________________________________
TonyN.:'                       <mailto:[email protected]>
      '                              <http://www.georgeanelson.com/>
_______________________________________________
Email-SIG mailing list
[email protected]
Your options: 
http://mail.python.org/mailman/options/email-sig/archive%40mail-archive.com

Reply via email to