bpo-33608: Use _Py_AddPendingCall() in _PyCrossInterpreterData_Release(). by ericsnowcurrently · Pull Request #12024 · python/cpython

Member

Use _Py_AddPendingCall() for releasing shared data.

416c522

Lock "HEAD" around looking up intepreter by ID.

466c0d9

Check the result of adding the pending call (for releasing XID).

e99a90b

Make a copy of data-to-be-deleted.

652413a

Revert: bpo-33608: Factor out a private, per-interpreter _Py_AddPendingCall(). (GH-11617) #12159

…ngCall(). (GH-11617) (GH-12159)

* Revert "bpo-36097: Use only public C-API in the_xxsubinterpreters module (adding as necessary). (#12003)"

This reverts commit bcfa450.

* Revert "bpo-33608: Simplify ceval's DISPATCH by hoisting eval_breaker ahead of time. (gh-12062)"

This reverts commit bda918b.

* Revert "bpo-33608: Use _Py_AddPendingCall() in _PyCrossInterpreterData_Release(). (gh-12024)"

This reverts commit b05b711.

* Revert "bpo-33608: Factor out a private, per-interpreter _Py_AddPendingCall(). (GH-11617)"

This reverts commit ef4ac96.

bpo-33608: Factor out a private, per-interpreter _Py_AddPendingCall(). #12360

gh-12360)

This is effectively an un-revert of #11617 and #12024 (reverted in #12159). Portions of those were merged in other PRs (with lower risk) and this represents the remainder. Note that I found 3 different bugs in the original PRs and have fixed them here.

bpo-33608: Factor out a private, per-interpreter _Py_AddPendingCall(). #13714