➜

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 BreamoreBoy, ajaksu2, barry, r.david.murray, rndblnch
Date 2010-12-02.22:36:03
SpamBayes Score 0.00032090335
Marked as misclassified No
Message-id <1291329379.03.0.880056265295.issue1672568@psf.upfronthosting.co.za>
In-reply-to
Content 
I've taken another look at this, and the email module is pretty consistent about just passing through data if it can't interpret it according to standards.  I think it would lead to a cluttered API if we add support for being strict and raising errors piecemeal.  So I'm deferring this to 3.3 and the email6 work, where we plan to have a comprehensive 'strict' mode.
History
Date User Action Args
2010-12-02 22:36:19r.david.murraysetrecipients: + r.david.murray, barry, rndblnch, ajaksu2, BreamoreBoy
2010-12-02 22:36:19r.david.murraysetmessageid: <1291329379.03.0.880056265295.issue1672568@psf.upfronthosting.co.za>
2010-12-02 22:36:03r.david.murraylinkissue1672568 messages
2010-12-02 22:36:03r.david.murraycreate