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 belopolsky
Recipients Alexander.Belopolsky, Arfrever, belopolsky, cvrebert, nagle, r.david.murray, roysmith
Date 2012-09-09.16:25:31
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> For what parts of ISO 8601 to accept, there's a standard: RFC3339

This is almost indistinguishable from the idea of accepting .isoformat() and str() results.  From what I see the only difference is that 't' is accepted for date/time separator and 'z' is accepted as a timezone.

Let's start with this.

As an ultimate solution, I would like to see something like codec registry so that we can do things like datetime(.., format='rfc3339') or date(.., format='gnu') for GNU parse_datetime.  I think this will look more pythonic than strptime().  Of course, strptime format can also be accepted as the value for the format keyword.
Date User Action Args
2012-09-09 16:25:32belopolskysetrecipients: + belopolsky, roysmith, nagle, Arfrever, r.david.murray, cvrebert, Alexander.Belopolsky
2012-09-09 16:25:32belopolskysetmessageid: <>
2012-09-09 16:25:32belopolskylinkissue15873 messages
2012-09-09 16:25:31belopolskycreate