Message169952
| Author |
Alexander.Belopolsky |
| Recipients |
Alexander.Belopolsky, belopolsky, nagle, r.david.murray |
| Date |
2012年09月06日.23:08:29 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<4E6188A8-5814-4257-91F7-B0C72654CE0C@gmail.com> |
| In-reply-to |
<1346966073.42.0.372075338364.issue15873@psf.upfronthosting.co.za> |
| Content |
%z format is supported, but it cannot accept colon in TZ offset. It can parse offsets like -0600 just fine. What OP is looking for is the GNU date %:z format which datetime does not support.
For ISO 8601 compliance, however I think we need a way to specify a parser that will accept any valid 8601 format: with T or space separator and with or without : in time and timezone and with or without dashes in date.
I would very much like such promiscuous parser to be implemented in datetime.__new__. So that we can create datetime objects from strings the way we do it with numbers. |
|