> > Can you please clarify where/when I should call PyEval_InitThreads()? Is
> > this in the main python thread before any pthread callbacks are generated?
> > If so, should this be done only once?
> Do it in your module init. That function is safe to be called multiple time.
>
I decided to do
> On 28 Oct 2020, at 15:22, Paul Grinberg wrote:
>
>
>>
>> Try calling PyEval_InitThreads() to force the python threading to be all
>> setup.
>
> Can you please clarify where/when I should call PyEval_InitThreads()? Is this
> in the main python thread before any pthread callbacks are gen
> Try calling PyEval_InitThreads() to force the python threading to be all
> setup.
Can you please clarify where/when I should call PyEval_InitThreads()? Is this
in the main python thread before any pthread callbacks are generated? If so,
should this be done only once?
--
https://mail.python.
> On 28 Oct 2020, at 13:25, Paul Grinberg wrote:
>
>>> I am running into unpredictable behavior with my Python extension module
>>> that wraps around a C++ library that starts a new pthread and, after doing
>>> some work, generates callbacks back into the caller. I've greatly
>>> simplified
> > I am running into unpredictable behavior with my Python extension module
> > that wraps around a C++ library that starts a new pthread and, after doing
> > some work, generates callbacks back into the caller. I've greatly
> > simplified this to a simplistic example which still demonstrates t
> On 27 Oct 2020, at 19:21, Paul Grinberg wrote:
>
> As full disclosure, I posted this question on StackOverflow as well, but it
> looks like questions with [Python] [Extension-Module] tags are not frequently
> answered. The link to my question there is
> https://stackoverflow.com/questions
