From: Georg Brandl Date: Mon, 6 Sep 2010 06:49:07 +0000 (+0000) Subject: #9780: both { and } are not valid fill characters. X-Git-Tag: v3.2a3~424 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=c86adb4c5c616e6aa7dcf9e59c71ba66ab5ea553;p=thirdparty%2FPython%2Fcpython.git #9780: both { and } are not valid fill characters. --- diff --git a/Doc/library/string.rst b/Doc/library/string.rst index cabb6f3815e0..f926924b1b72 100644 --- 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: