feat: support Python 3.11 by using _PyInternalFrame directly#137
Merged
Conversation
17dd89f to
d2a25b6
Compare
_PyInternalFrame_PyInternalFrame directly
c633f76 to
aabb823
Compare
d4d13e4 to
f4628ec
Compare
f4628ec to
244e7ca
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
feat: support Python 3.11 by using
_PyInternalFramedirectlyFixes #127
The
PyFrameObjectstructure members have been removed from the public C API in 3.11: https://docs.python.org/3/whatsnew/3.11.html#pyframeobject-3-11-hiding.Instead, getters are provided which participate in reference counting; since this code runs as part of the SIGPROF handler, it cannot modify Python objects (including their refcounts) and the getters can't be used. Instead, we expose the internal
_PyInterpreterFrameand use that directly.