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 llllllllll
Recipients josh.r, llllllllll, martin.panter, python-dev, serhiy.storchaka, vstinner, yselivanov
Date 2016-04-19.21:52:30
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1461102750.44.0.306650761644.issue26802@psf.upfronthosting.co.za>
In-reply-to
Content
CALL_FUNCTION doesn't use extended arg; I don't see what we get by adding some opcode to convert the sequence into a tuple. We also don't want to box up the stack arguments into a tuple because when we do a CALL_FUNCTION to a python function we just copy the stack[-n:] elements into the locals of the next frame. Emitting a build_tuple here would be an unneeded allocation.
History
Date User Action Args
2016-04-19 21:52:30llllllllllsetrecipients: + llllllllll, vstinner, python-dev, martin.panter, serhiy.storchaka, yselivanov, josh.r
2016-04-19 21:52:30llllllllllsetmessageid: <1461102750.44.0.306650761644.issue26802@psf.upfronthosting.co.za>
2016-04-19 21:52:30lllllllllllinkissue26802 messages
2016-04-19 21:52:30llllllllllcreate