Commit c86adb4c authored by Georg Brandl's avatar Georg Brandl

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

parent 9e75cad2
...@@ -299,11 +299,11 @@ The general form of a *standard format specifier* is: ...@@ -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:
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment