New submission from Guido van Rossum <gu...@python.org>:
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? ---------- messages: 325107 nosy: emilyemorehouse, gvanrossum priority: normal severity: normal status: open title: Curiosity: f((a)=1) is not a syntax error -- why? versions: Python 3.8 _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue34641> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
