Message170114
| Author | belopolsky |
|---|---|
| Recipients | Alexander.Belopolsky, Arfrever, belopolsky, cvrebert, nagle, r.david.murray, roysmith |
| Date | 2012-09-09.16:11:00 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1347207061.21.0.978594637144.issue15873@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
> I realize that while that is certainly an absolute lower bound, > it's almost certainly not sufficient. The most common use case > I see on a daily basis is parsing strings that look like > "2012-09-07T23:59:59+00:00". This is exactly what isoformat() of an aware datetime looks like: >>> datetime.now(timezone.utc).isoformat() '2012-09-09T16:09:46.165886+00:00' str() is the same up to T replaced by space: >>> print(datetime.now(timezone.utc)) 2012-09-09 15:19:12.567692+00:00 |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2012-09-09 16:11:01 | belopolsky | set | recipients: + belopolsky, roysmith, nagle, Arfrever, r.david.murray, cvrebert, Alexander.Belopolsky |
| 2012-09-09 16:11:01 | belopolsky | set | messageid: <1347207061.21.0.978594637144.issue15873@psf.upfronthosting.co.za> |
| 2012-09-09 16:11:00 | belopolsky | link | issue15873 messages |
| 2012-09-09 16:11:00 | belopolsky | create | |