From 7bcfd64f81ec7f7ba29b69a44b074c417a4b0e87 Mon Sep 17 00:00:00 2001 From: "Eric V. Smith" Date: Thu, 10 Sep 2015 04:03:33 -0400 Subject: [PATCH] After discussing with Guido, allow both 'f' and 'F'. --- pep-0498.txt | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/pep-0498.txt b/pep-0498.txt index 75a1ca7d0..9504e8780 100644 --- a/pep-0498.txt +++ b/pep-0498.txt @@ -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