[issue23316] Incorrect evaluation order of function arguments with *args
SilentGhost
report at bugs.python.org
Sun Jan 25 17:28:49 CET 2015
SilentGhost added the comment:
It seems, if I read https://docs.python.org/3/reference/expressions.html#calls correctly that the evaluation order of the function arguments is not defined in general, as it depends on your use of keyword argument and exact function signature. Naturally, f(a(), b()) would be evaluated in the order you're expecting.
----------
nosy: +SilentGhost
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue23316>
_______________________________________
More information about the Python-bugs-list
mailing list