GH-100987: Allow objects other than code objects as the "executable" of an internal frame.#105727
Uh oh!
There was an error while loading. Please reload this page.
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.
This is incomplete implementation of #100987. A full implementation will need a bit more discussion between producers of frames, Cython, MyPyc, etc and consumers, PySpy, Austin, etc.
Rather than wait for a full specification, this PR implements a limited version, as CPython is also a producer and consumer of frames, and we need this to simplify and speed optimizations.
Without this PR we need to create fake code objects for shims and other "artificial" frames, such as those introduced when specializing calls and operators.
This is a more limited version of #103010