[issue33216] CALL_FUNCTION_VAR

2018-04-03 Thread Manuel Vazquez Acosta
Change by Manuel Vazquez Acosta : -- nosy: mvaled priority: normal severity: normal status: open title: CALL_FUNCTION_VAR ___ Python tracker <https://bugs.python.org/issue33

[issue33216] Wrong order of stack for CALL_FUNCTION_VAR and CALL_FUNCTION_VAR_KW

2018-04-03 Thread Manuel Vazquez Acosta
New submission from Manuel Vazquez Acosta : The documentation of the dis module says that: CALL_FUNCTION_VAR (argc) Calls a function. *argc* is interpreted as in CALL_FUNCTION. The top elements on the stack are the keyword arguments, followed by the variable argument list, and then

[issue33216] Wrong order of stack for CALL_FUNCTION_VAR and CALL_FUNCTION_VAR_KW

2018-04-03 Thread Manuel Vazquez Acosta
Change by Manuel Vazquez Acosta : -- keywords: +patch pull_requests: +6075 stage: -> patch review ___ Python tracker <https://bugs.python.org/issue33216> ___ _

[issue33216] Wrong order of stack for CALL_FUNCTION_VAR and CALL_FUNCTION_VAR_KW

2018-04-03 Thread Manuel Vazquez Acosta
Manuel Vazquez Acosta added the comment: Correction, the documentation for CALL_FUNCTION_VAR said: Calls a function. *argc* is interpreted as in :opcode:`CALL_FUNCTION`. The top element on the stack contains the variable argument list, followed by keyword and positional arguments. In a