Message307330
> Is this fix released? I can't find it in the changelog…
Oops, I lost track of this issue, but it wasn't fixed, no.
I just proposed my old fix as a pull requets: PR 4650.
> (I faced this bug on 3.5.2, released a couple of months after this bug was closed…)
The workaround is to call PyEval_InitThreads() before spawning your first non-Python thread.
https://docs.python.org/dev/c-api/init.html#c.PyEval_InitThreads |
|
Date |
User |
Action |
Args |
2017-11-30 17:20:05 | vstinner | set | recipients:
+ vstinner, pitrou, Mekk, steve.dower, xcombelle |
2017-11-30 17:20:05 | vstinner | set | messageid: <1512062405.79.0.213398074469.issue20891@psf.upfronthosting.co.za> |
2017-11-30 17:20:05 | vstinner | link | issue20891 messages |
2017-11-30 17:20:05 | vstinner | create | |
|