➜

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 deronnax
Recipients Alexander.Belopolsky, Anders.Hovmöller, Arfrever, 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-02-15.04:02:30
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAKJVQ8_JpWgExWYCwdgUCjQ0cpOBZ+cAO8M3tUPRJu-tVJR7Hw@mail.gmail.com>
In-reply-to <1455505202.83.0.0826422118706.issue15873@psf.upfronthosting.co.za>
Content 
discarding the microseconds digits after the 6th.

2016-02-15 13:30 GMT+10:30 karl <report@bugs.python.org>:

>
> karl added the comment:
>
> About
>
> > Actually, I realized that the best implementation of parsing rfc 3339
> > is in django dateparse utils. To me it's the finest, the most
> > elegant, and no other one can claim to be more robust since it's
> > probably the #1 iso parsing functions used in python. Have a look at
> >
> https://docs.djangoproject.com/en/1.9/_modules/django/utils/dateparse/#parse_datetime
>
> How does it parse this date:
>
> 2016-02-15T11:59:46.16588638674+09:00
>
> ----------
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <http://bugs.python.org/issue15873>
> _______________________________________
>
History
Date User Action Args
2016-02-15 04:02:31deronnaxsetrecipients: + deronnax, barry, jcea, roysmith, belopolsky, nagle, vstinner, jwilk, mcepl, eric.araujo, Arfrever, r.david.murray, davydov, cvrebert, karlcow, Alexander.Belopolsky, perey, flying sheep, mihaic, berker.peksag, martin.panter, piotr.dobrogost, kirpit, Anders.Hovmöller, jstasiak, pbryan
2016-02-15 04:02:31deronnaxlinkissue15873 messages
2016-02-15 04:02:30deronnaxcreate