Skip to content

[3.7] bpo-33400: Clarified documentation to indicate no strict adherence to ISO 8601. (GH-6702)#6704

Merged
vsajip merged 1 commit into
python:3.7from
miss-islington:backport-c4994dc-3.7
May 28, 2018
Merged

[3.7] bpo-33400: Clarified documentation to indicate no strict adherence to ISO 8601. (GH-6702)#6704
vsajip merged 1 commit into
python:3.7from
miss-islington:backport-c4994dc-3.7

Conversation

@miss-islington

@miss-islington miss-islington commented May 4, 2018

Copy link
Copy Markdown
Contributor

(cherry picked from commit c4994dc)

Co-authored-by: Vinay Sajip vinay_sajip@yahoo.co.uk

https://bugs.python.org/issue33400

… ISO 8601. (pythonGH-6702)

(cherry picked from commit c4994dc)

Co-authored-by: Vinay Sajip <vinay_sajip@yahoo.co.uk>
@miss-islington

Copy link
Copy Markdown
Contributor Author

@vsajip: Backport status check is done, and it's a success ✅ .

Comment thread Doc/library/logging.rst
:func:`time.strftime` to format the creation time of the
record. Otherwise, the ISO8601 format is used. The resulting string is
returned.
record. Otherwise, an ISO8601-like (or RDC 3339-like) format is used. The

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

RFC ?

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Well spotted, thanks! Will correct.

@serhiy-storchaka

Copy link
Copy Markdown
Member

You can use the reStructuredText markup: :rfc:`3339`.

Comment thread Doc/howto/logging.rst
The default format for date/time display (shown above) is ISO8601. If you need
more control over the formatting of the date/time, provide a *datefmt*
argument to ``basicConfig``, as in this example::
The default format for date/time display (shown above) is like ISO8601 or

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is unnecessary. It is not "like" ISO8601, it is ISO 8601.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For now, I will sync the changes to be in line with the other branches, but won't close the issue. I think it's best just to state what the format is, make a reference to RFC 3339, and leave it at that. I will address this in a further update.

@vsajip vsajip merged commit eb8516b into python:3.7 May 28, 2018
@miss-islington

Copy link
Copy Markdown
Contributor Author

Thanks, @vsajip!

@miss-islington miss-islington deleted the backport-c4994dc-3.7 branch May 28, 2018 12:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants