➜

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 Anders.HovmÃķller
Recipients Alexander.Belopolsky, Anders.HovmÃķller, Arfrever, Eric.Hanchrow, Roman.Evstifeev, SilentGhost, aymeric.augustin, barry, belopolsky, berker.peksag, cvrebert, davydov, deronnax, eric.araujo, flying sheep, jcea, jstasiak, jwilk, karlcow, kirpit, martin.panter, mcepl, mihaic, nagle, pbryan, perey, piotr.dobrogost, r.david.murray, roysmith, vstinner
Date 2016-07-02.15:52:42
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <226B1846-CF0F-46C2-B4EA-AE2843A2D19F@killingar.net>
In-reply-to <1467469718.95.0.0767618634479.issue15873@psf.upfronthosting.co.za>
Content 
> 
> By the way, I just discovered, that the way we treat microseconds differs from the strptime one : we are smarter read every digits and smartly round to six, strptime doesn't go that far and just *truncate* to this. Should go that way, for consistency with what strptime does, maybe ?

I'm strongly against silently throwing away data and calling it even. If we want compatibility with strptime then it should be a separate flag like silent_truncate_milliseconds=True. 

On another matter: does the latest proposed code pass the tests in my ISO8601 implementation that I mentioned 2013 (! time flies)?
History
Date User Action Args
2016-07-02 15:52:42Anders.HovmÃķllersetrecipients: + Anders.HovmÃķller, barry, jcea, roysmith, belopolsky, nagle, vstinner, jwilk, mcepl, eric.araujo, Arfrever, r.david.murray, davydov, cvrebert, karlcow, SilentGhost, Alexander.Belopolsky, perey, flying sheep, mihaic, aymeric.augustin, Roman.Evstifeev, berker.peksag, martin.panter, piotr.dobrogost, kirpit, jstasiak, Eric.Hanchrow, deronnax, pbryan
2016-07-02 15:52:42Anders.HovmÃķllerlinkissue15873 messages
2016-07-02 15:52:42Anders.HovmÃķllercreate