Emily and I just discovered that f((a)=1) is accepted and compiled the same as f(a=1). This goes against the intention that keyword arguments have the syntax f(NAME=expr).I suspect that this behavior was introduced at the time we switched from generating from the (concrete) parse tree to first converting to an ast and then generating code from there. I.e. in the distant past (long before 2.7 even).But I still think it ought to be fixed. Thoughts? Anyone have an idea *where* to fix it?

I expect you'd have to make the check of test nodes in ast.c stricter. Here's a slightly gross implementation of that:diff --git a/Python/ast.c b/Python/ast.cindex94962e00c7..b7cebf4777 100644--- a/Python/ast.c+++ b/Python/ast.c@@ -2815,15 +2815,22 @@ ast_for_call(struct compiling *c, const node *n, expr_ty func, bool allowgen)                 identifier key, tmp;                 int k; -                /* chch is test, but must be an identifier? */-                e = ast_for_expr(c, chch);-                if (!e)+                static const int chain[] = {test, or_test, and_test, not_test, comparison, expr, xor_expr, and_expr, shift_expr, arith_expr, term, factor, power, atom_expr, atom, 0};++                node *expr_node = chch;+                for (int i = 0; chain[i]; i++) {+                    if (TYPE(expr_node) != chain[i])+                        break;+                    if (NCH(expr_node) != 1)+                        break;+                    expr_node = CHILD(expr_node, 0);+                }+                if (TYPE(expr_node) != NAME) {+                    ast_error(c, chch,+                            "keyword can't be an expression");                     return NULL;-                /* f(lambda x: x[0] = 3) ends up getting parsed with-                 * LHS test = lambda x: x[0], and RHS test = 3.-                 * SF bug 132313 points out that complaining about a keyword-                 * then is very confusing.-                 */+                }+                e = ast_for_expr(c, chch);                 if (e->kind == Lambda_kind) {                     ast_error(c, chch,                             "lambda cannot contain assignment");

There seems to be some of the similar cases that have tests added as part ofc960f26044edaea6669e60859ecf590c63c65e62 and the original error message added at3e0055f8c65c407e74ce476b8e2b1fb889723514.Existing tests : >>> f(x()=2)Traceback (most recent call last):SyntaxError: keyword can't be an expression>>> f(a or b=1)Traceback (most recent call last):SyntaxError: keyword can't be an expression>>> f(x.y=1)Traceback (most recent call last):SyntaxError: keyword can't be an expressionThanks

Could you please create a PR Benjamin? And please keep the comment about special casing lambda.See alsoissue30858 about the wording of the error message.

Tested the patch.➜  cpython git:(master) ✗ ./python.exePython 3.8.0a0 (heads/master-dirty:731ff68eee, Sep 12 2018, 11:40:16)[Clang 7.0.2 (clang-700.1.81)] on darwinType "help", "copyright", "credits" or "license" for more information.>>> def foo(a): pass...>>> foo((a)=1)  File "<stdin>", line 1SyntaxError: keyword can't be an expression➜  cpython git:(master) ✗ ./python.exe -m unittest -v test.test_syntaxtest_assign_call (test.test_syntax.SyntaxTestCase) ... oktest_assign_del (test.test_syntax.SyntaxTestCase) ... oktest_bad_outdent (test.test_syntax.SyntaxTestCase) ... oktest_break_outside_loop (test.test_syntax.SyntaxTestCase) ... oktest_global_param_err_first (test.test_syntax.SyntaxTestCase) ... oktest_kwargs_last (test.test_syntax.SyntaxTestCase) ... oktest_kwargs_last2 (test.test_syntax.SyntaxTestCase) ... oktest_kwargs_last3 (test.test_syntax.SyntaxTestCase) ... oktest_no_indent (test.test_syntax.SyntaxTestCase) ... oktest_nonlocal_param_err_first (test.test_syntax.SyntaxTestCase) ... oktest_unexpected_indent (test.test_syntax.SyntaxTestCase) ... ok----------------------------------------------------------------------Ran 11 tests in 0.006sOKThanks

New changesetc9a71dd223c4ad200a97aa320aef6bd3d45f8897 by Benjamin Peterson in branch 'master':closesbpo-34641: Further restrict the LHS of keyword argument function call syntax. (GH-9212)https://github.com/python/cpython/commit/c9a71dd223c4ad200a97aa320aef6bd3d45f8897