[issue1147646] Windows deadlock with PyEval_ReleaseLock
Amaury Forgeot d'Arc amaur...@gmail.com 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 rep...@bugs.python.org http://bugs.python.org/issue1147646 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1147646] Windows deadlock with PyEval_ReleaseLock
Mark Lawrence breamore...@yahoo.co.uk 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 rep...@bugs.python.org http://bugs.python.org/issue1147646 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1147646] Windows deadlock with PyEval_ReleaseLock
Changes by Mark Lawrence breamore...@yahoo.co.uk: -- versions: +Python 2.7, Python 3.1, Python 3.2 -Python 2.6 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1147646 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1147646] Windows deadlock with PyEval_ReleaseLock
Amaury Forgeot d'Arc amaur...@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 rep...@bugs.python.org http://bugs.python.org/issue1147646 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1147646] Windows deadlock with PyEval_ReleaseLock
Changes by Daniel Diniz aja...@gmail.com: -- 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 rep...@bugs.python.org http://bugs.python.org/issue1147646 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com