[issue33400] logging.Formatter does not default to ISO8601 date format

Vinay Sajip added the comment: New changeset 461ad598d12eba7754181402e00bb7cfc7f1d9cf by Vinay Sajip (Miss Islington (bot)) in branch '3.6': bpo-33400: Removed references to RFC3339 and ISO8601 from the logging documentation. (GH-7297) (GH-7303)

[issue33400] logging.Formatter does not default to ISO8601 date format

Vinay Sajip added the comment: New changeset 4b6691e40f004bf3a08b1843620f5f6028d2b79d by Vinay Sajip (Miss Islington (bot)) in branch '3.7': bpo-33400: Removed references to RFC3339 and ISO8601 from the logging documentation. (GH-7297) (GH-7302)

[issue33400] logging.Formatter does not default to ISO8601 date format

Change by miss-islington : -- pull_requests: +6934 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue33400] logging.Formatter does not default to ISO8601 date format

Change by miss-islington : -- pull_requests: +6933 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue33400] logging.Formatter does not default to ISO8601 date format

Change by Vinay Sajip : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___ ___

[issue33400] logging.Formatter does not default to ISO8601 date format

Vinay Sajip added the comment: New changeset 23cee80cfade1a9019c52b3a17d8e5c1b5db17e2 by Vinay Sajip in branch 'master': bpo-33400: Removed references to RFC3339 and ISO8601 from the logging documentation. (GH-7297)

[issue33400] logging.Formatter does not default to ISO8601 date format

Change by Vinay Sajip : -- pull_requests: +6926 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue33400] logging.Formatter does not default to ISO8601 date format

Paul Ganssle added the comment: 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.

[issue33400] logging.Formatter does not default to ISO8601 date format

Paul Ganssle added the comment: 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

[issue33400] logging.Formatter does not default to ISO8601 date format

Vinay Sajip added the comment: Because the specs allow certain decisions to be taken "by mutual consent", I'm not sure anyone can be really happy. Perhaps I should just state what the format actually is, as per msg316662, refer to RFC 3339 and leave it at that. I

[issue33400] logging.Formatter does not default to ISO8601 date format

Vinay Sajip added the comment: New changeset eb8516becc267caeb0ca6f9c41e805d1ba1caaa3 by Vinay Sajip (Miss Islington (bot)) in branch '3.7': bpo-33400: Clarified documentation to indicate no strict adherence to ISO 8601. (GH-6702) (GH-6704)

[issue33400] logging.Formatter does not default to ISO8601 date format

Vinay Sajip added the comment: Yes, sorry, Ned, I've been snowed under with other work recently :-( -- ___ Python tracker ___

[issue33400] logging.Formatter does not default to ISO8601 date format

Change by Ned Deily : -- versions: +Python 3.6, Python 3.7, Python 3.8 -Python 3.4 ___ Python tracker ___

[issue33400] logging.Formatter does not default to ISO8601 date format

Ned Deily added the comment: Vinay, PR_6704, the 3.7 backport is still unmerged with review comments and there are unresolved comments here. Can we at least get the 3.7 branch in sync with the other branches while you sort this out one way or another? -- nosy:

[issue33400] logging.Formatter does not default to ISO8601 date format

Paul Ganssle added the comment: I don't really agree with these changes to the documentation. The format that paulc identifies is actually an RFC 3339 datetime, which is a subset of ISO 8601, to the extent that you consider the fact that "we're using RFC 3339" is "mutual

[issue33400] logging.Formatter does not default to ISO8601 date format

Vinay Sajip added the comment: New changeset eb5abdc70815c4207829551ede4a7dc302d56c19 by Vinay Sajip (Miss Islington (bot)) in branch '3.6': bpo-33400: Clarified documentation to indicate no strict adherence to ISO 8601. (GH-6703)

[issue33400] logging.Formatter does not default to ISO8601 date format

Change by miss-islington : -- pull_requests: +6396 ___ Python tracker ___

[issue33400] logging.Formatter does not default to ISO8601 date format

Change by miss-islington : -- pull_requests: +6395 ___ Python tracker ___

[issue33400] logging.Formatter does not default to ISO8601 date format

Vinay Sajip added the comment: New changeset c4994dc00d9828a99510f3851da93b0e1c18361d by Vinay Sajip in branch 'master': bpo-33400: Clarified documentation to indicate no strict adherence to ISO 8601. (GH-6702)

[issue33400] logging.Formatter does not default to ISO8601 date format

Change by Vinay Sajip : -- keywords: +patch pull_requests: +6394 stage: -> patch review ___ Python tracker ___

[issue33400] logging.Formatter does not default to ISO8601 date format

Paul Ganssle added the comment: ISO 8601 does not require an offset (in fact, most portions of the ISO 8601 date and time are optional - ISO 8601 is more complicated than most people think). Without an offset a datetime is assumed to be local time. The T delimiter is

[issue33400] logging.Formatter does not default to ISO8601 date format

Change by Ned Deily : -- nosy: +vinay.sajip ___ Python tracker ___ ___ Python-bugs-list

[issue33400] logging.Formatter does not default to ISO8601 date format

New submission from Paul Cyr : >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