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 p-ganssle
Recipients p-ganssle, paulc, vinay.sajip
Date 2018-05-15.15:02:41
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1526396561.42.0.682650639539.issue33400@psf.upfronthosting.co.za>
In-reply-to
Content
I don't really agree with these changes to the documentation.

The format that paulc identifies is actually an RFC 3339 datetime, which is a subset of ISO 8601, to the extent that you consider the fact that "we're using RFC 3339" is "mutual consent" for omitting the `T` separator. The changes to the documentation make it more confusing because it's not clear how precisely the datetime is considered to deviate from the spec.

I think I would change the documentation to refer to the format as RFC 3339 and if ISO 8601 is mentioned at all, it can be parenthetical in the first mention.

In any case, exposing the spec like this would probably be useful:

YYYY-MM-DD HH:MM:SS,mmm

The fact that this complies with the RFC 3339 spec (particularly as commonly implemented) just means "an ISO parser that implements the spec should be able to read this".
History
Date User Action Args
2018-05-15 15:02:41p-gansslesetrecipients: + p-ganssle, vinay.sajip, paulc
2018-05-15 15:02:41p-gansslesetmessageid: <1526396561.42.0.682650639539.issue33400@psf.upfronthosting.co.za>
2018-05-15 15:02:41p-gansslelinkissue33400 messages
2018-05-15 15:02:41p-gansslecreate