[issue39984] Move pending calls from _PyRuntime to PyInterpreterState

Change by STINNER Victor : -- components: +Subinterpreters -Interpreter Core ___ Python tracker ___ ___ Python-bugs-list mailing lis

[issue39984] Move pending calls from _PyRuntime to PyInterpreterState

STINNER Victor added the comment: > I reopen the issue because of bpo-40082 "trip_signal() gets NULL tstate on > Windows on CTRL+C" regression. bpo-40082 is fixed, so I close the issue again. -- resolution: -> fixed status: open -> closed ___ Pyt

[issue39984] Move pending calls from _PyRuntime to PyInterpreterState

STINNER Victor added the comment: I reopen the issue because of bpo-40082 "trip_signal() gets NULL tstate on Windows on CTRL+C" regression. -- resolution: fixed -> status: closed -> open ___ Python tracker ___

[issue39984] Move pending calls from _PyRuntime to PyInterpreterState

STINNER Victor added the comment: > Awesome! Thanks for doing this, Victor. I'll take a look when I can and > adjust the changes for bpo-33608. If you'll recall, I made a similar change > as part of the solution for that issue, which we later reverted due to > problems we discovered with

[issue39984] Move pending calls from _PyRuntime to PyInterpreterState

Eric Snow added the comment: Awesome! Thanks for doing this, Victor. I'll take a look when I can and adjust the changes for bpo-33608. If you'll recall, I made a similar change as part of the solution for that issue, which we later reverted due to problems we discovered with daemon thread

[issue39984] Move pending calls from _PyRuntime to PyInterpreterState

STINNER Victor added the comment: I moved pending calls to PyInterpreterState. There are remaining issues with using pending calls in subinterpreters, but I propose to continue the discussion in bpo-37127. -- resolution: -> fixed stage: patch review -> resolved status: open -> close