➜

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 brett.cannon, serhiy.storchaka, vstinner
Date 2016-12-09.18:00:49
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1481306450.73.0.124326033178.issue28924@psf.upfronthosting.co.za>
In-reply-to
Content 
Inline PyEval_EvalFrameEx() in callers. The PEP 523 modified PyEval_EvalFrameEx(): it's now an indirection to interp->eval_frame().

Inline the call in performance critical code. Leave PyEval_EvalFrame() unchanged, this function is only kept for backward compatibility (and so not important for performance).

I pushed directly my change as the revision 99c34e47348b, but it broke test_gdb. So now I doubt that it's 100% "safe" to inline the code. Outside test_gdb, does something else rely on PyEval_EvalFrameEx()? So I chose to open an issue to discuss the change. By "something", I'm thinking to Pyjion :-)

Attached patch updates also python-gdb.py to fix test_gdb.
History
Date User Action Args
2016-12-09 18:00:50vstinnersetrecipients: + vstinner, brett.cannon, serhiy.storchaka
2016-12-09 18:00:50vstinnersetmessageid: <1481306450.73.0.124326033178.issue28924@psf.upfronthosting.co.za>
2016-12-09 18:00:50vstinnerlinkissue28924 messages
2016-12-09 18:00:50vstinnercreate