New submission from Matthieu Dartiailh: The computation of the stack_effect of the CALL_FUNCTION_EX does not reflect the use of the argument to the opcode.
Currently stack_effect expect two flags (one on 0x01 and one on 0x02) corresponding to whether positional arguments and keyword arguments are being passed. However in the current implementation the argument of CALL_FUNCTION_EX is either 0 or 1 depending on the presence of keyword arguments. According to Serhiy Storchaka, the behavior of stack_effect is a left-over of the previous implementation and should be fixed. ---------- components: Interpreter Core messages: 288230 nosy: mdartiailh priority: normal severity: normal status: open title: Broken stack_effect for CALL_FUNCTION_EX type: behavior versions: Python 3.6, Python 3.7 _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue29607> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
