certain f/t-string expressions not copied correctly to debug str or interpolations

Bug report

Bug description:

The function set_ftstring_expr() in Parser/lexer/lexer.c does not currently copy certain f/t-string expressions correctly. It has problems with non-coding quotes (escaped or in comments) and nested f/t-strings. This applies to both self-documenting debug expressions and more importantly to t-string interpolation expressions.

For example, the # comment below should not print:

>>> print(f'''{'\'' # comment
... =}''')
'\'' # comment
="'"

Copied expression terminates early:

>>> print(f'{(f'''
... # not comment A
... { # comment B '
... 3 # comment C
... * 2}''', '\n# not comment D\n6')=}')
(f'''
# not comment A
{ # comment B '
3
* 2}''', '\n('\n# not comment A\n6', '\n# not comment D\n6')

It does not appear the function was written to handle nested f/t-strings and the string quote handling does not take into account escaped quotes.

CPython versions tested on:

3.14, CPython main branch

Operating systems tested on:

Linux

Linked PRs

• gh-141274

Inizia in Parser/lexer/lexer.c, in set_ftstring_expr(), e riproduci gli esempi del report con virgolette con escape, commenti e f/t-string annidate. Traccia il modo in cui le espressioni vengono copiate per l’output di debug e l’interpolazione delle t-string, quindi verifica che il testo tra virgolette e i commenti non interrompano la copia in anticipo e che gli output mostrati siano corretti.