Message109765
This issue looks invalid to me: PyEval_ReleaseLock manipulates the interpreter lock, but not the thread state.
Both have to be released/reset before another thread can install its own thread state and run.
In other words, PyEval_SaveThread() should be used instead (and PyEval_RestoreThread() at the end, but the example code does not care to finalize the interpreter) |
|
Date |
User |
Action |
Args |
2010-07-09 16:38:03 | amaury.forgeotdarc | set | recipients:
+ amaury.forgeotdarc, montulli, BreamoreBoy |
2010-07-09 16:38:03 | amaury.forgeotdarc | set | messageid: <1278693483.37.0.975443660062.issue1147646@psf.upfronthosting.co.za> |
2010-07-09 16:38:01 | amaury.forgeotdarc | link | issue1147646 messages |
2010-07-09 16:38:00 | amaury.forgeotdarc | create | |
|