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:55:25
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1527512125.58.0.682650639539.issue33400@psf.upfronthosting.co.za>
In-reply-to
Content
Ah, actually, my mistake, RFC 3339 most assuredly *does* require a UTC offset:


   4.4. Unqualified Local Time

   A number of devices currently connected to the Internet run their
   internal clocks in local time and are unaware of UTC.  While the
   Internet does have a tradition of accepting reality when creating
   specifications, this should not be done at the expense of
   interoperability.  Since interpretation of an unqualified local time
   zone will fail in approximately 23/24 of the globe, the
   interoperability problems of unqualified local time are deemed
   unacceptable for the Internet.  Systems that are configured with a
   local time, are unaware of the corresponding UTC offset, and depend
   on time synchronization with other Internet systems, MUST use a
   mechanism that ensures correct synchronization with UTC.  Some
   suitable mechanisms are:


This is not true of ISO 8601, but dropping all references to RFC 3339 or ISO 8601 is fine with me.
History
Date User Action Args
2018-05-28 12:55:25p-gansslesetrecipients: + p-ganssle, vinay.sajip, ned.deily, paulc
2018-05-28 12:55:25p-gansslesetmessageid: <1527512125.58.0.682650639539.issue33400@psf.upfronthosting.co.za>
2018-05-28 12:55:25p-gansslelinkissue33400 messages
2018-05-28 12:55:25p-gansslecreate