bpo-40334: Spacialized error message for invalid args after bare '*'

[lysnikolaou]

When parsing things like def f(*): pass or lambda *: pass the old parser used to
output SyntaxError: named arguments must follow bare *, which the
new parser wasn't able to do.

https://bugs.python.org/issue40334

[gvanrossum]

Okay, good as-is.

On Sat, May 2, 2020 at 14:10 Lysandros Nikolaou ***@***.***> wrote: ***@***.**** commented on this pull request. ------------------------------ In Grammar/python.gram <#19865 (comment)>: > +invalid_star_etc: + | '*' (')' | ',' (')' | '**')) { RAISE_SYNTAX_ERROR("named arguments must follow bare *") } +invalid_lambda_star_etc: + | '*' (':' | ',' (':' | '**')) { RAISE_SYNTAX_ERROR("named arguments must follow bare *") } Or would that be too weird? Your call. IMHO it'd be a bit more difficult to understand a rule like that. "What's the colon doing there?" — You are receiving this because your review was requested. Reply to this email directly, view it on GitHub <#19865 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAWCWMTWMXUGRVJ5MSXVSETRPSD2XANCNFSM4MXZI7PA> .

-- --Guido (mobile)