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 paulc
Recipients paulc
Date 2018-05-01.19:37:24
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1525203444.89.0.682650639539.issue33400@psf.upfronthosting.co.za>
In-reply-to
Content
From the docs:

https://docs.python.org/3.6/library/logging.html#logging.Formatter

"class logging.Formatter(fmt=None, datefmt=None, style='%') ...
If no datefmt is specified, the ISO8601 date format is used."

However, the output from the formatter when no datefmt is specified is not an ISO8601 date. It is also a datetime format, not a date format.

Example output: 2018-05-01 19:04:31,505

Not being an ISO member, I don't have access to the official source for the specification but, trusting other sources, it appears that the output is missing the required 'T' delimiter between the date and time, and it is also missing the timezone. A compliant output would be:

2018-05-01T19:04:31,505Z

The current output appears to actually be closer to RFC 3339, as that standards allows for a space instead of the 'T' delimiter, but RFC 3339 still requires a timezone.

Either the documentation should be updated to state that the format used is an RFC 3339 datetime but without a timezone, or the format should comply with the standard specified in the documentation.
History
Date User Action Args
2018-05-01 19:37:24paulcsetrecipients: + paulc
2018-05-01 19:37:24paulcsetmessageid: <1525203444.89.0.682650639539.issue33400@psf.upfronthosting.co.za>
2018-05-01 19:37:24paulclinkissue33400 messages
2018-05-01 19:37:24paulccreate