[issue33492] Updating the Evaluation order section to cover *expression in calls
New submission from Martijn Pieters <mj@python.org>: Can the *Evaluation order* (_evalorder) section in reference/expressions.rst please be updated to cover this exception in a *call* primary (quoting from the _calls section): A consequence of this is that although the ``*expression`` syntax may appear *after* explicit keyword arguments, it is processed *before* the keyword arguments (and any ``**expression`` arguments -- see below). So:: This exception to the normal expression evaluation order is rather buried in the _calls section only. ---------- assignee: docs@python components: Documentation messages: 316494 nosy: docs@python, mjpieters priority: normal severity: normal status: open title: Updating the Evaluation order section to cover *expression in calls versions: Python 3.5, Python 3.6, Python 3.7, Python 3.8 _______________________________________ Python tracker <report@bugs.python.org> <https://bugs.python.org/issue33492> _______________________________________
Change by Eric Lebigot <eric.lebigot@normalesup.org>: ---------- nosy: +Eric Lebigot _______________________________________ Python tracker <report@bugs.python.org> <https://bugs.python.org/issue33492> _______________________________________
Change by Terry J. Reedy <tjreedy@udel.edu>: ---------- versions: -Python 3.5 _______________________________________ Python tracker <report@bugs.python.org> <https://bugs.python.org/issue33492> _______________________________________
participants (3)
-
Eric Lebigot
-
Martijn Pieters
-
Terry J. Reedy