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 ned.deily, p-ganssle, paulc, vinay.sajip
Date 2018-05-28.12:49:05
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1527511745.39.0.682650639539.issue33400@psf.upfronthosting.co.za>
In-reply-to
Content
I think this is more a matter of misunderstanding the fact that ISO 8601 is a larger and more complicated spec than people think.  You'll note that the original complaint also seems to think that a timezone is required (it is not). You can find a copy of RFC 3339 here: https://tools.ietf.org/html/rfc3339

Which states:


      NOTE: ISO 8601 defines date and time separated by "T".
      Applications using this syntax may choose, for the sake of
      readability, to specify a full-date and full-time separated by
      (say) a space character.

I think this is sufficient to refer to this as an RFC 3339 datetime, as a spec-compliant parser should be able to handle it just fine. Then there is no need for "x-like" anywhere in the documentation, which is just confusing. I do agree that the precise spec should be given.
History
Date User Action Args
2018-05-28 12:49:05p-gansslesetrecipients: + p-ganssle, vinay.sajip, ned.deily, paulc
2018-05-28 12:49:05p-gansslesetmessageid: <1527511745.39.0.682650639539.issue33400@psf.upfronthosting.co.za>
2018-05-28 12:49:05p-gansslelinkissue33400 messages
2018-05-28 12:49:05p-gansslecreate