Just clarify there's no problem about calling twice to PyEval_InitThreads ()
as indicated by Python's doc.
> Hi,
>
>
>
> Maybe you already fixed the issue, but for the record, I've got the same
>
> problem and finally it turned out that I was calling PyEval_InitThreads twice
>
> and also afte
Hi,
Maybe you already fixed the issue, but for the record, I've got the same
problem and finally it turned out that I was calling PyEval_InitThreads twice
and also after fixing that, I also had to move the call to
PyEval_ReleaseLock(); at the end of the entire initialization (not just after
PyE
On 17/05/2012 10:08 PM, shooshx wrote:
I'm embedding python in a multi-threaded C application.
I've taken care to wrap every call to the Python C API with
gstate = PyGILState_Ensure();
// call python code
PyGILState_Release(gstate);
But I'm stumped with what to do in the initialization.
Right a
I'm embedding python in a multi-threaded C application.
I've taken care to wrap every call to the Python C API with
gstate = PyGILState_Ensure();
// call python code
PyGILState_Release(gstate);
But I'm stumped with what to do in the initialization.
Right after the call to Py_IsInitialized() I've
