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

This commit is contained in:
Georg Brandl 2010-09-06 06:49:07 +00:00
parent 9e75cad234
commit c86adb4c5c

View file

@ -299,11 +299,11 @@ The general form of a *standard format specifier* is:
precision: `integer` precision: `integer`
type: "b" | "c" | "d" | "e" | "E" | "f" | "F" | "g" | "G" | "n" | "o" | "s" | "x" | "X" | "%" 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 The *fill* character can be any character other than '{' or '}'. The presence
end of the field). The presence of a fill character is signaled by the *next* of a fill character is signaled by the character following it, which must be
character, which must be one of the alignment options. If the second character one of the alignment options. If the second character of *format_spec* is not
of *format_spec* is not a valid alignment option, then it is assumed that both a valid alignment option, then it is assumed that both the fill character and
the fill character and the alignment option are absent. the alignment option are absent.
The meaning of the various alignment options is as follows: The meaning of the various alignment options is as follows: