[issue41064] Specialise syntax error of **dict in f-string field

Pablo Galindo Salgado added the comment: New changeset 8efad61963809d239cac986e3f3bc4cb505ab8fe by Pablo Galindo in branch 'master': bpo-41064: Improve syntax error for invalid usage of '**' in f-strings (GH-25006)

[issue41064] Specialise syntax error of **dict in f-string field

Change by Pablo Galindo Salgado : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue41064] Specialise syntax error of **dict in f-string field

Pablo Galindo Salgado added the comment: > I don't recall if this is really only a "skip leading whitespace" problem, or > if there's some other reason they're required. IIRC, this forces the expression inside to be parsed as an expression. This helps the quite a lot the parser. For

[issue41064] Specialise syntax error of **dict in f-string field

Change by Pablo Galindo Salgado : -- keywords: +patch pull_requests: +23764 stage: -> patch review pull_request: https://github.com/python/cpython/pull/25006 ___ Python tracker

[issue41064] Specialise syntax error of **dict in f-string field

Eric V. Smith added the comment: 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

[issue41064] Specialise syntax error of **dict in f-string field

Terry J. Reedy added the comment: Cressey noted both a compile and IDLE Shell issue. They must be handled separately by different people in separate bpo issues. The first is about the helpful versus less helpful SyntaxError messages in the following (master compiled today). >>> f'{*x}'