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, mcspang, r.david.murray
Date 2011-03-24.13:55:42
SpamBayes Score 3.275158e-13
Marked as misclassified No
Message-id <>
I needed an airplane-trip-sized problem to work on on the way back from PyCon and the sprints, so I tried my hand at "fixing" this.  The attached patch is really just a proof of concept.  Because it is so invasive of the email package machinery I doubt that I will apply it, but it does serve to prove that it is quite practical, given the right design, to preserve the leading whitespace in message headers, and this does enable the email package to read and write the messages in the sample mbox without changing them.  I will incorporate what I learned from this exercise into the header management in email6.

On the other hand, if anyone else thinks this *is* worth tidying up an applying I could be convinced.

Note that after this patch one test fails, but that test failure is actually a buggy test that hides a bug in the header formatter (a failure to provide folding white space at the start of a continuation line).  That bug I may revisit.
Date User Action Args
2011-03-24 13:55:43r.david.murraysetrecipients: + r.david.murray, barry, mcspang
2011-03-24 13:55:43r.david.murraysetmessageid: <>
2011-03-24 13:55:43r.david.murraylinkissue1590744 messages
2011-03-24 13:55:42r.david.murraycreate