[issue9900] Threading Bug or misuse of the api ?

2010-09-19 Thread Rob Watson
Rob Watson added the comment: it seemed changing PyEval_ReleaseLock() to PyThreadState_DeleteCurrent() has fixed my problem. Thanks -- resolution: invalid -> ___ Python tracker <http://bugs.python.org/iss

[issue9900] Threading Bug or misuse of the api ?

2010-09-19 Thread Rob Watson
Changes by Rob Watson : -- status: open -> closed ___ Python tracker <http://bugs.python.org/issue9900> ___ ___ Python-bugs-list mailing list Unsubscri

[issue9900] Threading Bug or misuse of the api ?

2010-09-19 Thread Rob Watson
Changes by Rob Watson : -- status: closed -> open ___ Python tracker <http://bugs.python.org/issue9900> ___ ___ Python-bugs-list mailing list Unsubscri

[issue9900] Threading Bug or misuse of the api ?

2010-09-19 Thread Rob Watson
Changes by Rob Watson : -- resolution: invalid -> ___ Python tracker <http://bugs.python.org/issue9900> ___ ___ Python-bugs-list mailing list Unsubscri

[issue9900] Threading Bug or misuse of the api ?

2010-09-19 Thread Rob Watson
Changes by Rob Watson : -- resolution: -> invalid status: open -> closed ___ Python tracker <http://bugs.python.org/issue9900> ___ ___ Python-bugs-list

[issue9900] Threading Bug or misuse of the api ?

2010-09-19 Thread Rob Watson
New submission from Rob Watson : Is the below a bug or a misuse of the api ? This was compiled with visual studio 2008 and python26 64bit void testfunction() { for (int x = 1;x <= 10;x++) { PyGILState_STATE gstate = PyGILState_Ens