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 gvanrossum
Recipients Joshua.Landau, NeilGirdhar, SilentGhost, gvanrossum, iritkatriel, r.david.murray, terry.reedy
Date 2021-06-16.18:17:22
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1623867442.92.0.678645759595.issue23316@roundup.psfhosted.org>
In-reply-to
Content
> "The one exception is in function calls with *expression after a keyword argument: f(x=expr2, *expr1)."

So the question before us is whether to add this phrase to the docs, or to tweak the compiler to fix it. It is certainly convenient to update the docs rather than expend the resources to change the compiler for what looks like a rare corner case.

How certain are we that this is truly the only exception? Can someone read the compiler source code related to argument order, or experiment with all the different permutations of positional args, keyword args, *args, and **kwargs? (Fortunately the evaluation order is independent from the function definition, so it's really just all permutations of those four things.)
History
Date User Action Args
2021-06-16 18:17:22gvanrossumsetrecipients: + gvanrossum, terry.reedy, r.david.murray, SilentGhost, Joshua.Landau, NeilGirdhar, iritkatriel
2021-06-16 18:17:22gvanrossumsetmessageid: <1623867442.92.0.678645759595.issue23316@roundup.psfhosted.org>
2021-06-16 18:17:22gvanrossumlinkissue23316 messages
2021-06-16 18:17:22gvanrossumcreate