➜

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 belopolsky, cvrebert, davydov, eric.araujo, ezio.melotti, martin.panter, mihaic, mribecky, r.david.murray, tinchester
Date 2014-06-16.16:34:08
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1402936448.46.0.345995551822.issue5207@psf.upfronthosting.co.za>
In-reply-to
Content 
Supporting ISO 8601 is quite different from supporting RFC2822 dates, as far as I can see, and the latter clearly belongs in the email library (especially considering that RFC2822 parsing must follow Postel's Law and accept "dirty" data).  

If you want to open an issue to add ISO 8601 support (as opposed to RFC 3339's 8601 profile+timezone-deviation that is already covered by issue 15873) to datetime, go ahead.  I haven't read enough to understand the details, so I don't know quite what that would mean, or how useful it would be.
History
Date User Action Args
2014-06-16 16:34:08r.david.murraysetrecipients: + r.david.murray, belopolsky, mribecky, ezio.melotti, eric.araujo, davydov, cvrebert, mihaic, martin.panter, tinchester
2014-06-16 16:34:08r.david.murraysetmessageid: <1402936448.46.0.345995551822.issue5207@psf.upfronthosting.co.za>
2014-06-16 16:34:08r.david.murraylinkissue5207 messages
2014-06-16 16:34:08r.david.murraycreate