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 eric.smith
Recipients JNCressey, epaine, eric.smith, pablogsal, terry.reedy
Date 2021-03-23.08:04:03
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1616486643.74.0.555465018475.issue41064@roundup.psfhosted.org>
In-reply-to
Content
The parens are added in fstring_compile_expr at https://github.com/python/cpython/blob/9feae41c4f04ca27fd2c865807a5caeb50bf4fc4/Parser/string_parser.c#L391

I don't recall if this is really only a "skip leading whitespace" problem, or if there's some other reason they're required. If it's just a whitespace issue, maybe skipping leading whitespace in fstring_compile_expr is a better idea? One of the reasons I originally didn't want to skip leading whitespace is because I didn't want to add yet another place where we'd have to maintain a "what qualifies as whitespace to the compiler?" decision.
History
Date User Action Args
2021-03-23 08:04:03eric.smithsetrecipients: + eric.smith, terry.reedy, pablogsal, epaine, JNCressey
2021-03-23 08:04:03eric.smithsetmessageid: <1616486643.74.0.555465018475.issue41064@roundup.psfhosted.org>
2021-03-23 08:04:03eric.smithlinkissue41064 messages
2021-03-23 08:04:03eric.smithcreate