[Python-Dev] Issue 20891 - PyGILState_Ensure on non-Python thread causes fatal error (original) (raw)
Steve Dower Steve.Dower at microsoft.com
Tue Mar 11 19:48:56 CET 2014
- Previous message: [Python-Dev] Whats New in 3.4 is pretty much done...
- Next message: [Python-Dev] Requesting pronouncement on PEP 463: Exception-catching expressions
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi python-dev
Just wanted to draw some attention to http://bugs.python.org/issue20891, which I just created. (I hope I got the right people on the nosy list, but going broad just to be safe.)
Details and the discussion can go on there, but the basic gist is that C threads can't safely call PyGILState_Ensure() any more unless PyEval_InitThreads() has been called from an existing Python thread - you get a fatal error because there is no current thread state. Since PyGILState_Ensure is supposed to create this thread state, I believe this is a serious regression and would really like to see it fixed before 3.4 is released.
Cheers, Steve
- Previous message: [Python-Dev] Whats New in 3.4 is pretty much done...
- Next message: [Python-Dev] Requesting pronouncement on PEP 463: Exception-catching expressions
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]