Author vstinner
Recipients Mark.Shannon, brett.cannon, dino.viehland, eric.snow, fabioz, gregory.p.smith, lukasz.langa, phsilva, vstinner
Date 2020-03-12.17:52:25
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1584035545.16.0.983782453051.issue38500@roundup.psfhosted.org>
In-reply-to
Content
Mark:
> PEP 523 is quite vague, but the rationale indicates that exposing `eval_frame` is for "a method-level JIT". PEP 523 did not suggest adding an API.

I disagree, the PEP is quite explicit: "Third-party code may then set their own frame evaluation function instead to control the execution of Python code." That's the whole point of the PEP: let third-party code set eval_frame to use the feature.

The PEP was written in 2016, when the PyInterpreterState structure was part of the public C API. But PyInterpreterState was moved to the internal C API, after the PEP was approved.
History
Date User Action Args
2020-03-12 17:52:25vstinnersetrecipients: + vstinner, brett.cannon, gregory.p.smith, fabioz, phsilva, dino.viehland, lukasz.langa, Mark.Shannon, eric.snow
2020-03-12 17:52:25vstinnersetmessageid: <1584035545.16.0.983782453051.issue38500@roundup.psfhosted.org>
2020-03-12 17:52:25vstinnerlinkissue38500 messages
2020-03-12 17:52:25vstinnercreate