Message260294
| Author | karlcow |
|---|---|
| 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.03:00:02 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1455505202.83.0.0826422118706.issue15873@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
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 |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2016-02-15 03:00:02 | karlcow | set | recipients: + karlcow, barry, jcea, roysmith, belopolsky, nagle, vstinner, jwilk, mcepl, eric.araujo, Arfrever, r.david.murray, davydov, cvrebert, Alexander.Belopolsky, perey, flying sheep, mihaic, berker.peksag, martin.panter, piotr.dobrogost, kirpit, Anders.Hovmöller, jstasiak, deronnax, pbryan |
| 2016-02-15 03:00:02 | karlcow | set | messageid: <1455505202.83.0.0826422118706.issue15873@psf.upfronthosting.co.za> |
| 2016-02-15 03:00:02 | karlcow | link | issue15873 messages |
| 2016-02-15 03:00:02 | karlcow | create | |