[issue37186] Everyone uses GIL wrong! = DEADLOCK

Eric Snow report at bugs.python.org
Fri Jun 7 13:29:01 EDT 2019


Eric Snow <ericsnowcurrently at gmail.com> added the comment:

The situation with subinterpreters and the gilstate API is a known problem (see issues #10915 and #15751).  We plan on fixing that in the near future for 3.9 (and probably for 3.8).  Feel free to chime in on those earlier issues.  Note that the subinterpreter experience is going to be much improved with the 3.9 release.

You also mentioned an issue with PyEval_AcquireThread().  If you don't think this is directly related to the gilstate API (I suspect it is) then please open a new issue for that.

----------
resolution:  -> duplicate
stage:  -> resolved
status: open -> closed
superseder:  -> Make the PyGILState API compatible with multiple interpreters

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37186>
_______________________________________


More information about the Python-bugs-list mailing list