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 nagle
Recipients Anders.Hovmöller, Arfrever, Eric.Hanchrow, Roman.Evstifeev, SilentGhost, aymeric.augustin, barry, belopolsky, berker.peksag, cvrebert, davydov, deronnax, eric.araujo, flying sheep, gvanrossum, jcea, jstasiak, jwilk, karlcow, kirpit, martin.panter, mcepl, mihaic, nagle, pbryan, perey, piotr.dobrogost, r.david.murray, roysmith, shanmbic, sirex, sonots, tim.peters, vstinner, ztane
Date 2017-07-27.18:31:44
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
As the original author of the predecessor bug report (issue 15873) in 2012, I would suggest that there's too much bikeshedding here. I filed this bug because there was no usable ISO8601 date parser available.  PyPi contained four slightly different buggy ones, and three more versions were found later.  

I suggested following RFC3339, "Date and Time on the Internet: Timestamps", section 5.6, which specifies a clear subset of ISO8601.  Five years later, I suggest just going with that. Fancier variations belong in non-standard libraries.

Date parsing should not be platform-dependent.  Using an available C library was convenient, but not portable. 

Let's get this done.
Date User Action Args
2017-07-27 18:31:45naglesetrecipients: + nagle, gvanrossum, tim.peters, barry, jcea, roysmith, belopolsky, vstinner, jwilk, mcepl, eric.araujo, Arfrever, r.david.murray, davydov, cvrebert, karlcow, SilentGhost, perey, flying sheep, mihaic, aymeric.augustin, Roman.Evstifeev, berker.peksag, martin.panter, piotr.dobrogost, kirpit, ztane, Anders.Hovmöller, jstasiak, Eric.Hanchrow, deronnax, pbryan, shanmbic, sirex, sonots
2017-07-27 18:31:45naglesetmessageid: <>
2017-07-27 18:31:45naglelinkissue24954 messages
2017-07-27 18:31:44naglecreate