https://github.com/python/cpython/commit/445152e0d3ab6e4381aef8d1404c2c17a51... commit: 445152e0d3ab6e4381aef8d1404c2c17a516070f branch: 3.8 author: Miss Islington (bot) <31488909+miss-islington@users.noreply.github.com> committer: GitHub <noreply@github.com> date: 2020-02-28T12:06:53-08:00 summary: bpo-13790: Change 'string' to 'specification' in format doc (GH-18690) (cherry picked from commit 916895f93905f8b8dad677cceff501833f5a633a) Co-authored-by: Terry Jan Reedy <tjreedy@udel.edu> files: A Misc/NEWS.d/next/Documentation/2020-02-28-14-39-25.bpo-13790.hvLaRI.rst M Doc/library/string.rst diff --git a/Doc/library/string.rst b/Doc/library/string.rst index 89c169a512b52..fa906f799c108 100644 --- a/Doc/library/string.rst +++ b/Doc/library/string.rst @@ -302,9 +302,9 @@ specification is to be interpreted. Most built-in types implement the following options for format specifications, although some of the formatting options are only supported by the numeric types. -A general convention is that an empty format string (``""``) produces +A general convention is that an empty format specification produces the same result as if you had called :func:`str` on the value. A -non-empty format string typically modifies the result. +non-empty format specification typically modifies the result. The general form of a *standard format specifier* is: diff --git a/Misc/NEWS.d/next/Documentation/2020-02-28-14-39-25.bpo-13790.hvLaRI.rst b/Misc/NEWS.d/next/Documentation/2020-02-28-14-39-25.bpo-13790.hvLaRI.rst new file mode 100644 index 0000000000000..77db173168fc5 --- /dev/null +++ b/Misc/NEWS.d/next/Documentation/2020-02-28-14-39-25.bpo-13790.hvLaRI.rst @@ -0,0 +1 @@ +Change 'string' to 'specification' in format doc.