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.

Author mdartiailh
Recipients mdartiailh
Date 2017-02-20.19:50:38
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1487620239.38.0.547704987013.issue29607@psf.upfronthosting.co.za>
In-reply-to
Content
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.
History
Date User Action Args
2017-02-20 19:50:39mdartiailhsetrecipients: + mdartiailh
2017-02-20 19:50:39mdartiailhsetmessageid: <1487620239.38.0.547704987013.issue29607@psf.upfronthosting.co.za>
2017-02-20 19:50:39mdartiailhlinkissue29607 messages
2017-02-20 19:50:38mdartiailhcreate