#9780: both { and } are not valid fill characters.

c86adb4c · Georg Brandl · 9e75cad2 · c86adb4c
Commit c86adb4c authored Sep 06, 2010 by Georg Brandl
Hide whitespace changes
Inline Side-by-side

Showing with 5 additions and 5 deletions

Doc/library/string.rst Doc/library/string.rst +5 -5

No files found.
--- a/Doc/library/string.rst
+++ b/Doc/library/string.rst
@@ -299,11 +299,11 @@ The general form of a *standard format specifier* is:
   precision: `integer`
   type: "b" | "c" | "d" | "e" | "E" | "f" | "F" | "g" | "G" | "n" | "o" | "s" | "x" | "X" | "%"

-The *fill* character can be any character other than '}' (which signifies the
-end of the field).  The presence of a fill character is signaled by the *next*
-character, which must be one of the alignment options. If the second character
-of *format_spec* is not a valid alignment option, then it is assumed that both
-the fill character and the alignment option are absent.
+The *fill* character can be any character other than '{' or '}'.  The presence
+of a fill character is signaled by the character following it, which must be
+one of the alignment options.  If the second character of *format_spec* is not
+a valid alignment option, then it is assumed that both the fill character and
+the alignment option are absent.

 The meaning of the various alignment options is as follows: