NotificationsYou must be signed in to change notification settings
Fork33.4k
Star69.8k

[3.14] Document`Py_AddPendingCall()` change with subinterpreters in 3.12 (GH-139117)#139118

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.

By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Jump to bottom

Merged

hugovk merged 1 commit intopython:3.14frommiss-islington:backport-89ff88b-3.14

Oct 3, 2025

Merged

[3.14] Document`Py_AddPendingCall()` change with subinterpreters in 3.12 (GH-139117)#139118

hugovk merged 1 commit intopython:3.14frommiss-islington:backport-89ff88b-3.14

Oct 3, 2025

Conversation

Copy link

Contributor

miss-islington commentedSep 18, 2025•
edited by github-actionsbot
Loading

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. InGH-104813, this was undone, so Py_AddPendingCall() would always schedule for the main interpreter.
(cherry picked from commit89ff88b)

Co-authored-by: Peter Biermazintensitydev@gmail.com

📚 Documentation preview 📚:https://cpython-previews--139118.org.readthedocs.build/

DocumentPy_AddPendingCall()change with subinterpreters in 3.12 (p…

ea36d03

…ythonGH-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. InpythonGH-104813, this was undone, so Py_AddPendingCall() would always schedule for the main interpreter.(cherry picked from commit89ff88b)Co-authored-by: Peter Bierma <zintensitydev@gmail.com>