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.

Title: Updating the Evaluation order section to cover *expression in calls
Type: Stage:
Components: Documentation Versions: Python 3.8, Python 3.7, Python 3.6
Status: open Resolution:
Dependencies: Superseder:
Assigned To: docs@python Nosy List: Eric Lebigot, docs@python, mjpieters
Priority: normal Keywords:

Created on 2018-05-14 08:14 by mjpieters, last changed 2022-04-11 14:59 by admin.

Messages (1)
msg316494 - (view) Author: Martijn Pieters (mjpieters) * Date: 2018-05-14 08:14
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.
Date User Action Args
2022-04-11 14:59:00adminsetgithub: 77673
2018-05-18 17:36:41terry.reedysetversions: - Python 3.5
2018-05-15 10:35:20Eric Lebigotsetnosy: + Eric Lebigot
2018-05-14 08:14:24mjpieterscreate