Thanks to visit codestin.com
Credit goes to github.com

Skip to content
Open
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
pyframe fix 8
  • Loading branch information
Yashp002 committed Feb 5, 2026
commit 43e9c9f02c8d7d6e676e3f03a2d3d42fc9d79c78
5 changes: 2 additions & 3 deletions Doc/c-api/frame.rst
Original file line number Diff line number Diff line change
Expand Up @@ -274,10 +274,9 @@ Unless using :pep:`523`, you will not need this.

.. code-block:: c

// Check if a frame should be skipped
int kind = PyUnstable_Frame_GetExecutableKind(frame)

if (kind == PyUnstable_EXECUTABLE_KIND_SKIP) {
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What is kind? How do you get it?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@encukou kind here refers to the executable kind field stored in the frame's executor (e.g. _PyFrame_GetExecutableKind(frame))
Do you think it's better to explicitly show _PyFrame_GetExecutableKind (if exposed), or should I just remove the example block to avoid confusion?

Copy link
Copy Markdown
Member

@encukou encukou Feb 3, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, explicitly show your _PyFrame_GetExecutableKind. We'll also need to make it public (or at least unstable) if we want users to use it.

// This is an internal frame (like a Tier 2 optimizer frame)
// Tools should ignore it.
continue;
}

Expand Down
Loading