-
-
Notifications
You must be signed in to change notification settings - Fork 31.8k
bad logging documentation {}-formatting placeholder #109451
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Please, send a PR :) |
AlberLC
added a commit
to AlberLC/cpython
that referenced
this issue
Sep 15, 2023
vsajip
pushed a commit
that referenced
this issue
Sep 16, 2023
miss-islington
pushed a commit
to miss-islington/cpython
that referenced
this issue
Sep 16, 2023
…ythonGH-109465) (cherry picked from commit 929cc4e) Co-authored-by: AlberLC <[email protected]>
miss-islington
pushed a commit
to miss-islington/cpython
that referenced
this issue
Sep 16, 2023
…ythonGH-109465) (cherry picked from commit 929cc4e) Co-authored-by: AlberLC <[email protected]>
vsajip
pushed a commit
that referenced
this issue
Sep 16, 2023
…GH-109465) (GH-109482) (cherry picked from commit 929cc4e)
Yhg1s
pushed a commit
that referenced
this issue
Sep 17, 2023
…GH-109465) (#109483) gh-109451: Fix wrong format specifier in logging documentation (GH-109465) (cherry picked from commit 929cc4e) Co-authored-by: AlberLC <[email protected]>
csm10495
pushed a commit
to csm10495/cpython
that referenced
this issue
Sep 28, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Documentation
%-formatting (It works)
example.log:
✅
Now using the the modern {} format syntax, as the documentation says (doesn't work)
❌
Exception:
Proposed fix
Use
{msecs:03.0f}
placeholder.example.log:
✅
Linked PRs
The text was updated successfully, but these errors were encountered: