summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorGeorg Brandl <georg@python.org>2010-09-06 06:49:07 (GMT)
committerGeorg Brandl <georg@python.org>2010-09-06 06:49:07 (GMT)
commitc86adb4c5c616e6aa7dcf9e59c71ba66ab5ea553 (patch)
tree77fe9ec5d88e239b08170a1e47c4f6d27c71f41e
parent9e75cad23473cb5562ffbb05ac3fa23714b8663b (diff)
downloadcpython-c86adb4c5c616e6aa7dcf9e59c71ba66ab5ea553.zip
cpython-c86adb4c5c616e6aa7dcf9e59c71ba66ab5ea553.tar.gz
cpython-c86adb4c5c616e6aa7dcf9e59c71ba66ab5ea553.tar.bz2
#9780: both { and } are not valid fill characters.
-rw-r--r--Doc/library/string.rst10
1 files changed, 5 insertions, 5 deletions
diff --git a/Doc/library/string.rst b/Doc/library/string.rst
index cabb6f3..f926924 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: