This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author davidhalter
Recipients davidhalter, eric.smith
Date 2018-06-03.14:22:54
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
As I wrote before, I'm not trying to change anything about the f-string behavior. It is a refactoring. If anyone wants to change the behavior, I feel like they should probably write a PEP anyway.

I personally don't like that f-strings get parsed multiple times. It just smells bad. Also f-strings are IMO not just strings. They should maybe look like strings for other tools to parse them. But they are more or less statements that get executed.

The code in ast.c is not bad. Don't get me wrong. I just think that it's the wrong approach.

Regarding the edge cases: I don't think there are that many. In the end the ast output will look similar anyway. All the backslashes, string literals and comments can be checked and rejected in the tokenizer already.
Date User Action Args
2018-06-03 14:22:54davidhaltersetrecipients: + davidhalter, eric.smith
2018-06-03 14:22:54davidhaltersetmessageid: <>
2018-06-03 14:22:54davidhalterlinkissue33754 messages
2018-06-03 14:22:54davidhaltercreate