➜

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.

classification
Title: email Parser non-strict mode
Type: Stage:
Components: Extension Modules Versions:
process
Status: closed Resolution: accepted
Dependencies: Superseder:
Assigned To: barry Nosy List: anthonybaxter, barry
Priority: normal Keywords: patch

Created on 2002-06-06 07:02 by anthonybaxter, last changed 2022-04-10 16:05 by admin. This issue is now closed.

Files
File name Uploaded Description Edit
parser.diff anthonybaxter, 2002-06-06 08:09 newer parser.diff
Messages (3)
msg40225 - (view) Author: Anthony Baxter (anthonybaxter) (Python triager) Date: 2002-06-06 07:02 
Here's my current state of the non-strict Parser mode.
At the moment it handles most ugly stuff I see, with the
exception of the multiple-nested-multiparts-with the same
boundary tags grossness - but I think that this is actually
a pretty savage violation of the RFC, so I'm not too fussed
about it.

There's still some work to be done in the area of digests,
but I'll bring that up on mimelib-devel.
msg40226 - (view) Author: Anthony Baxter (anthonybaxter) (Python triager) Date: 2002-06-06 08:09 
Logged In: YES 
user_id=29957

Here's a newer version of the patch that gets digests right,
as I talked about on mimelib-devel. The code that gets digests
right should be split out of this in any case - I'd look
into splitting
it, but I've got too much on my plate right now.
msg40227 - (view) Author: Barry A. Warsaw (barry) * (Python committer) Date: 2002-07-09 01:45 
Logged In: YES 
user_id=12800

I've got this integrated with my copy now and will likely
check it in.  Any possibility you can send me some unit tests?
History
Date User Action Args
2022-04-10 16:05:23adminsetgithub: 36701
2002-06-06 07:02:38anthonybaxtercreate