After discussing with Guido, allow both 'f' and 'F'.
This commit is contained in:
parent
5572aeccab
commit
7bcfd64f81
|
@ -170,10 +170,11 @@ Specification
|
|||
=============
|
||||
|
||||
In source code, f-strings are string literals that are prefixed by the
|
||||
letter 'f'. 'f' may be combined with 'r', in either order, to produce
|
||||
raw f-string literals. 'f' may not be combined with 'b': this PEP does
|
||||
not propose to add binary f-strings. 'f' may also be combined with
|
||||
'u', in either order, although adding 'u' has no effect.
|
||||
letter 'f' or 'F'. Everywhere this PEP uses 'f', 'F' may also be
|
||||
used. 'f' may be combined with 'r', in either order, to produce raw
|
||||
f-string literals. 'f' may not be combined with 'b': this PEP does not
|
||||
propose to add binary f-strings. 'f' may also be combined with 'u', in
|
||||
either order, although adding 'u' has no effect.
|
||||
|
||||
When tokenizing source files, f-strings use the same rules as normal
|
||||
strings, raw strings, binary strings, and triple quoted strings. That
|
||||
|
|
Loading…
Reference in New Issue