You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A while back we moved the pending calls to PyInterpreterState. Then in 2020 we made it so pending calls would only run in the main thread of the main interpreter. Doing so renders the per-interpreter pending calls state pointless and prevents us from making use of pending calls for subinterpreters.
We also need to look at how to handle overflow when the number of pending calls reaches NPENDINGCALLS, whether bumping the number, or moving to a linked list, or something else.
Activity
ericsnowcurrently commentedon May 23, 2023
We also need to look at how to handle overflow when the number of pending calls reaches
NPENDINGCALLS, whether bumping the number, or moving to a linked list, or something else.ericsnowcurrently commentedon Jun 5, 2023
maybe related: gh-84412
gh-104812: Run Pending Calls in any Thread (gh-104813)
pythongh-104812: Run Pending Calls in any Thread (pythongh-104813)
pythongh-104812: Run Pending Calls in any Thread (pythongh-104813)
gh-104812: Skip Pending Calls Tests if No Threading (gh-105761)
[3.12] gh-104812: Run Pending Calls in any Thread (gh-104813) (gh-105752
Skip test_enable_max_threads on free-threading builds