➜

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 mirabilos
Recipients belopolsky, mirabilos, mirkovogt, r.david.murray
Date 2015-02-27.14:02:57
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1425045778.14.0.447067064059.issue23332@psf.upfronthosting.co.za>
In-reply-to
Content 
Hm, RFCs are just RFCs and not standards, they can recommend whatever they want, and they can (and do) contradict each other.

I’ve seen things (mostly related to eMail and PIM synchronisation) that require ‘Z’ for UTC proper.

Additionally, +00:00 can be UTC, but it can also be British Winter Time, or DST of UTC-1. ‘Z’ is clear.
History
Date User Action Args
2015-02-27 14:02:58mirabilossetrecipients: + mirabilos, belopolsky, r.david.murray, mirkovogt
2015-02-27 14:02:58mirabilossetmessageid: <1425045778.14.0.447067064059.issue23332@psf.upfronthosting.co.za>
2015-02-27 14:02:58mirabiloslinkissue23332 messages
2015-02-27 14:02:57mirabiloscreate