STINNER Victor <victor.stin...@gmail.com> added the comment: > Is this fix released? I can't find it in the changelog…
Oops, I lost track of this issue, but it wasn't fixed, no. I just proposed my old fix as a pull requets: PR 4650. > (I faced this bug on 3.5.2, released a couple of months after this bug was > closed…) The workaround is to call PyEval_InitThreads() before spawning your first non-Python thread. https://docs.python.org/dev/c-api/init.html#c.PyEval_InitThreads ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue20891> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
