[issue1147646] Windows deadlock with PyEval_ReleaseLock

Amaury Forgeot d'Arc report at bugs.python.org
Fri Jul 9 18:38:03 CEST 2010

Amaury Forgeot d'Arc <amauryfa at gmail.com> added the comment:

This issue looks invalid to me: PyEval_ReleaseLock manipulates the interpreter lock, but not the thread state.
Both have to be released/reset before another thread can install its own thread state and run.

In other words, PyEval_SaveThread() should be used instead (and PyEval_RestoreThread() at the end, but the example code does not care to finalize the interpreter)

nosy: +amaury.forgeotdarc

Python tracker <report at bugs.python.org>

More information about the Python-bugs-list mailing list