This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author r.david.murray
Recipients barry, georg.brandl, r.david.murray
Date 2012-06-24.08:52:56
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1340527988.81.0.399006538534.issue15160@psf.upfronthosting.co.za>
In-reply-to
Content
I've been working on this steadily for a while.  I think it is now all working correctly.  At least, it passes all the same tests that the existing RFC mime header parser passes, plus a bunch of additional ones.

There are a couple of commented out tests where there are issues with the folding.  The folding doesn't normally get invoked for headers parsed from source, and the cases are marginal anyway (headers with invalid binary data) so I'm not worried about them, but will fix them after the beta.

There are things that can be done to make this API even more convenient, but I think this is a solid foundation worth having.  And the parser is a full RFC parser, so it handles cases that the current parser doesn't.  (There are also probably cases where it fails when the current parser doesn't, but I haven't found them yet ;)
History
Date User Action Args
2012-06-24 08:53:09r.david.murraysetrecipients: + r.david.murray, barry, georg.brandl
2012-06-24 08:53:08r.david.murraysetmessageid: <1340527988.81.0.399006538534.issue15160@psf.upfronthosting.co.za>
2012-06-24 08:53:07r.david.murraylinkissue15160 messages
2012-06-24 08:53:07r.david.murraycreate