classification
Title: Windows deadlock with PyEval_ReleaseLock
Type: behavior Stage: test needed
Components: Windows Versions: Python 2.6
process
Status: open Resolution:
Dependencies: Superseder:
Assigned To: Nosy List: montulli (1)
Priority: normal Keywords

Created on 2005-02-22 19:04 by montulli, last changed 2009-02-16 01:01 by ajaksu2.

Messages (1)
msg60673 - (view) Author: Lou Montulli (montulli) Date: 2005-02-22 19:04 
This problem is described well by this post from '03
http://mail.python.org/pipermail/python-dev/2003-August/037729.html

The problem still seems to exist.  The solution
described within the post will not work in all cases
because if you do not call  PyEval_ReleaseLock then
other threads will be deadlocked, and if you do call
PyEval_ReleaseLock, the thread that originally called
InitThreads will be deadlocked.  The only work around
that I have found so far is to use a separate thread
that will never call scripts call InitThreads and then
 PyEval_ReleaseLock.  After that all threads will run
correctly, but the thread that originally called
InitThreads cannot run python.

Feel free to contact me for any other details, or call
me a bonehead if I screwed something up.  lou a
montulli o org
History
Date User Action Args
2009-02-16 01:01:10ajaksu2settitle: Windows deadlock with PyEval_ReleaseLock -> Windows deadlock with PyEval_ReleaseLock
stage: test needed
type: behavior
versions: + Python 2.6, - Python 2.4
2005-02-22 19:04:55montullicreate