[issue1147646] Windows deadlock with PyEval_ReleaseLock

Amaury Forgeot d'Arc added the comment: This is actually the same issue as issue1720250 -- resolution: -> duplicate status: open -> closed superseder: -> PyGILState_Ensure does not acquires GIL ___ Python tracker

[issue1147646] Windows deadlock with PyEval_ReleaseLock

Amaury Forgeot d'Arc 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 u

[issue1147646] Windows deadlock with PyEval_ReleaseLock

Changes by Mark Lawrence : -- versions: +Python 2.7, Python 3.1, Python 3.2 -Python 2.6 ___ Python tracker ___ ___ Python-bugs-list

[issue1147646] Windows deadlock with PyEval_ReleaseLock

Mark Lawrence added the comment: Anyone with Windows threading experience who could comment on this please, i.e. is it still an issue? -- nosy: +BreamoreBoy ___ Python tracker __

[issue1147646] Windows deadlock with PyEval_ReleaseLock

Changes by Daniel Diniz : -- stage: -> test needed title: Windows deadlock with PyEval_ReleaseLock -> Windows deadlock with PyEval_ReleaseLock type: -> behavior versions: +Python 2.6 -Python 2.4 ___ Python tracker