[ python-Bugs-1147646 ] Windows deadlock with PyEval_ReleaseLock

[SourceForge.net]

Bugs item #1147646, was opened at 2005-02-22 11:04
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1147646&group_id=5470

Category: Windows
Group: Python 2.4
Status: Open
Resolution: None
Priority: 5
Submitted By: Lou Montulli (montulli)
Assigned to: Nobody/Anonymous (nobody)
Summary: Windows deadlock with PyEval_ReleaseLock 

Initial Comment:
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

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1147646&group_id=5470