Python 3.12 released

Can you please explain what you are referring to?

Because political with small "p" is an inescapable fact of life? Unless, of course, you choose to go and live on a desert island (and even there, you have the problem of uninvited visitors).

Cheers,
Wol

> Now it seems the parser will just start huting for a matching bracket in a random quote following the f-string, isn't that error-prone if not downright dangerous?

No, it isn't, because there's no "in a random quote" rule. The matching bracket does not have to be quoted, and in fact it is an error to quote it. Officially, f"FOO{expr}BAR" is parsed into these parts:

f"
FOO
{expr}
BAR
"

expr is interpreted as if it is not inside of any quoted context (the braces temporarily "cancel" the enclosing quotes). But in practice, you could just as validly interpret it like this:

f"FOO{
expr
}BAR"

In other words, you *could* think of the braces as matching (and temporarily "closing") the quotes, even though they formally don't, because it turns out that that produces the same overall behavior (provided the braces are also properly balanced). This also works for nested contexts like f"FOO{f"bar{"BAZ"}qux"}THE_END":

f"FOO{
f"bar{
"BAZ"
}qux"
}THE_END"

(This is a very silly example, because you could just concatenate all of the string literals and write one big string literal instead.)

However, the opening and closing quotes do have to match, so you can't write f"FOO{expr}BAR' (the single quote does not match the double quote). If you want to think of the left brace as temporarily closing the quote, then the right brace should be considered to reopen the same quote (rather than opening a brand-new quote).

It would all be more readable with balanced quotation marks “ and ”

It's kind of a historical accident that most programming languages have ended up with the same character to open and close a quoted string.