]> git.ipfire.org Git - thirdparty/Python/cpython.git/commitdiff
bpo-13790: Change 'string' to 'specification' in format doc (GH-18690)
authorMiss Islington (bot) <31488909+miss-islington@users.noreply.github.com>
Fri, 28 Feb 2020 20:04:19 +0000 (12:04 -0800)
committerGitHub <noreply@github.com>
Fri, 28 Feb 2020 20:04:19 +0000 (12:04 -0800)
(cherry picked from commit 916895f93905f8b8dad677cceff501833f5a633a)

Co-authored-by: Terry Jan Reedy <tjreedy@udel.edu>
Doc/library/string.rst
Misc/NEWS.d/next/Documentation/2020-02-28-14-39-25.bpo-13790.hvLaRI.rst [new file with mode: 0644]

index 6cbe54963196af84f179b29bbe620a525203224d..ed8c912364c477efc62fd704b34c8be3e04c3682 100644 (file)
@@ -303,9 +303,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 (file)
index 0000000..77db173
--- /dev/null
@@ -0,0 +1 @@
+Change 'string' to 'specification' in format doc.