New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bpo-45923: Handle call events in bytecode #30364
bpo-45923: Handle call events in bytecode #30364
Conversation
|
Ah, you did something I suggested a while back: instead of the |
|
Might even be a bit faster although I suspect that is just random fluctuations. |
Looks mostly good! I like the direction we're headed in with this stuff.
Just a few questions:
|
When you're done making the requested changes, leave the comment: And if you don't make the requested changes, you will be poked with soft cushions! |
|
Merging this now to get it into 3.11a4 and provide a fix/workaround for https://bugs.python.org/issue46225 |
This PR:
Adds a
RESUMEinstruction which is a no-op unless tracing is active.This replaces the current approach of testing for tracing on every call or resume.
In itself this has no real effect, but will enable faster dispatch and more streamlined tracing in the future.
No significant impact on performance
https://bugs.python.org/issue45923
The text was updated successfully, but these errors were encountered: