Skip to content

[3.11] GH-93252: Fix error handling for failed Python calls (GH-94693) #94707

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.

Sign up for GitHub

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

Closed
tiran wants to merge 2 commits into from
Closed

[3.11] GH-93252: Fix error handling for failed Python calls (GH-94693) #94707

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
305cfe8
[3.11] GH-93252: Fix error handling for failed Python calls (GH-94693)
brandtbucher Jul 9, 2022
a1ec06d
Drop assert, 3.11 does not have co_framesize from GH-93908
tiran Jul 9, 2022
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
Drop assert, 3.11 does not have co_framesize from GH-93908
  • Loading branch information
@tiran
tiran committed Jul 9, 2022
commit a1ec06d67bcb6679b912de6927bb2dd6114d7c9c
2 changes: 0 additions & 2 deletions Python/ceval.c
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6394,8 +6394,6 @@ _PyEvalFrameClearAndPop(PyThreadState *tstate, _PyInterpreterFrame * frame)
{
// Make sure that this is, indeed, the top frame. We can't check this in
// _PyThreadState_PopFrame, since f_code is already cleared at that point:
assert((PyObject **)frame + frame->f_code->co_framesize ==
tstate->datastack_top);
tstate->recursion_remaining--;
assert(frame->frame_obj == NULL || frame->frame_obj->f_frame == frame);
assert(frame->owner == FRAME_OWNED_BY_THREAD);
Expand Down