-
-
Notifications
You must be signed in to change notification settings - Fork 33.4k
bpo-47045: Remove f_state field, and make ownership of _PyInterpreterFrame explicit.
#31963
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
Conversation
|
🤖 New build scheduled with the buildbot fleet by @markshannon for commit 1be0129 🤖 If you want to schedule another build, you need to add the ":hammer: test-with-buildbots" label again. |
|
🤖 New build scheduled with the buildbot fleet by @markshannon for commit 3cf7d0a 🤖 If you want to schedule another build, you need to add the ":hammer: test-with-buildbots" label again. |
|
🤖 New build scheduled with the buildbot fleet by @markshannon for commit 5225175 🤖 If you want to schedule another build, you need to add the ":hammer: test-with-buildbots" label again. |
|
Buildbot failures are unrelated to this PR. |
The main purpose of this change is to avoid having to update
f_statein the interpreter, with the ultimate aim of removingRESUMEinstructions.However, removing
f_statemakes it difficult to handle clearing and freeing frames owned by generators and frame objects.So, I've had to add the
ownerfield to make it explicit who owns the memory in a_PyInterpreterFrameFinally, we now track the kind of tracing event on the thread state. This seems to be necessary to maintain the semantics of
frame.set_lineno.https://bugs.python.org/issue47045