Skip to content

[3.13] Document Py_AddPendingCall() change with subinterpreters in 3.12 (GH-139117) #139119

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

Merged
ZeroIntensity merged 1 commit into from
Sep 18, 2025
Merged

[3.13] Document Py_AddPendingCall() change with subinterpreters in 3.12 (GH-139117) #139119

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
Document Py_AddPendingCall() change with subinterpreters in 3.12 (G… 
…H-139117)

Prior to 3.9, Py_AddPendingCall() would always run pending calls in the main interpreter, but then each interpreter got their own ceval state, and they were scheduled for any interpreter. In GH-104813, this was undone, so Py_AddPendingCall() would always schedule for the main interpreter.
(cherry picked from commit 89ff88b)

Co-authored-by: Peter Bierma <zintensitydev@gmail.com>
  • Loading branch information
@ZeroIntensity @miss-islington
ZeroIntensity authored and miss-islington committed Sep 18, 2025
commit a1ca2f5bfe945b3263257eef48f68668927b8e37
4 changes: 4 additions & 0 deletions Doc/c-api/init.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1944,6 +1944,10 @@ pointer and a void pointer argument.
called from the main interpreter. Each subinterpreter now has its own
list of scheduled calls.

.. versionchanged:: 3.12
This function now always schedules *func* to be run in the main
interpreter.

.. _profiling:

Profiling and Tracing
Expand Down
Loading