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 vstinner
Recipients matrixise, rhettinger, serhiy.storchaka, vstinner
Date 2016-11-25.14:08:21
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1480082901.4.0.232296609913.issue28800@psf.upfronthosting.co.za>
In-reply-to
Content
> Do you want to add RETURN_NONE or RETURN_CONST? Or both?

Only RETURN_NONE because on some corner cases it allow to avoid completely the None constant from code.co_consts and reduce the stack size.

I'm not sure that I want to start taking the same road of WPython which added a *lot* of specialized instructions (combining two or more existing instructions). As you said, it has a cost on the maintenance, and might have a negative impact if _PyEval_EvalFrameDefault() becomes too big.
History
Date User Action Args
2016-11-25 14:08:21vstinnersetrecipients: + vstinner, rhettinger, serhiy.storchaka, matrixise
2016-11-25 14:08:21vstinnersetmessageid: <1480082901.4.0.232296609913.issue28800@psf.upfronthosting.co.za>
2016-11-25 14:08:21vstinnerlinkissue28800 messages
2016-11-25 14:08:21vstinnercreate