[issue33492] Updating the Evaluation order section to cover *expression in calls

[Terry J. Reedy]

Change by Terry J. Reedy :


--
versions:  -Python 3.5

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue33492] Updating the Evaluation order section to cover *expression in calls

[Eric Lebigot]

Change by Eric Lebigot :


--
nosy: +Eric Lebigot

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue33492] Updating the Evaluation order section to cover *expression in calls

[Martijn Pieters]

New submission from Martijn Pieters :

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 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com