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 poolie
Recipients ajaksu2, belopolsky, daniel.urban, eric.araujo, l0nwlf, mihaic, poolie, r.david.murray, techtonik
Date 2011-08-22.06:41:01
SpamBayes Score 1.2096295e-08
Marked as misclassified No
Message-id <>
Z is well established as meaning "UTC time" <> so shouldn't be used for "zone not known."  rfc 3393 is clear that it's equivalent to +00:00.  

So the questions seem to be:
 * should there be an included battery to do this format at all?
 * should it represent utc as '+00:00' or as 'Z' by default - applications should have the choice.

It's probably reasonable to assume correct Python application code using datetime objects will know whether they have a local, utc, or unknown time.

The current patch does not seem to have any way to format an object with a declared UTC tzinfo as having a 'Z' prefix, which would be useful.
Date User Action Args
2011-08-22 06:41:03pooliesetrecipients: + poolie, belopolsky, techtonik, ajaksu2, eric.araujo, r.david.murray, daniel.urban, l0nwlf, mihaic
2011-08-22 06:41:02pooliesetmessageid: <>
2011-08-22 06:41:01poolielinkissue7584 messages
2011-08-22 06:41:01pooliecreate