mirror of
https://github.com/python/cpython.git
synced 2025-10-02 05:12:23 +00:00
[3.11] [doc] Improve grammar/fix missing word (GH-102060) (GH-102277)
[doc] Improve grammar/fix missing word (GH-102060)
(cherry picked from commit 6daf42b28e
)
Co-authored-by: VMan <vayidm@users.noreply.github.com>
This commit is contained in:
parent
626f471d88
commit
2c4fc87ac1
2 changed files with 2 additions and 2 deletions
|
@ -70,7 +70,7 @@ Click on the "New issue" button in the top bar to report a new issue.
|
|||
The submission form has two fields, "Title" and "Comment".
|
||||
|
||||
For the "Title" field, enter a *very* short description of the problem;
|
||||
less than ten words is good.
|
||||
fewer than ten words is good.
|
||||
|
||||
In the "Comment" field, describe the problem in detail, including what you
|
||||
expected to happen and what did happen. Be sure to include whether any
|
||||
|
|
|
@ -2538,7 +2538,7 @@ should be logged, or the ``extra`` keyword parameter to indicate additional
|
|||
contextual information to be added to the log). So you cannot directly make
|
||||
logging calls using :meth:`str.format` or :class:`string.Template` syntax,
|
||||
because internally the logging package uses %-formatting to merge the format
|
||||
string and the variable arguments. There would no changing this while preserving
|
||||
string and the variable arguments. There would be no changing this while preserving
|
||||
backward compatibility, since all logging calls which are out there in existing
|
||||
code will be using %-format strings.
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue