I ran into a problem with PyGILState_Rele ase under Python < 2.4.2,
that forced me to call PyEval_InitThre ads() in my extension module.
2.4.2 had a fix for that problem :"It is now safe to call
PyGILState_Rele ase() before PyEval_InitThre ads()" (from the NEWS
file).
I can live with this call, but I was wondering if there isn't a better
way. As PyEval_ThreadsI nitialized is not available either, it seems
there is no way to know if threads have been initialized.
Thanks!
--
Thomas
that forced me to call PyEval_InitThre ads() in my extension module.
2.4.2 had a fix for that problem :"It is now safe to call
PyGILState_Rele ase() before PyEval_InitThre ads()" (from the NEWS
file).
I can live with this call, but I was wondering if there isn't a better
way. As PyEval_ThreadsI nitialized is not available either, it seems
there is no way to know if threads have been initialized.
Thanks!
--
Thomas