➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author amaury.forgeotdarc
Recipients BreamoreBoy, amaury.forgeotdarc, montulli
Date 2010-07-09.16:38:00
SpamBayes Score 0.0027359724
Marked as misclassified No
Message-id <1278693483.37.0.975443660062.issue1147646@psf.upfronthosting.co.za>
In-reply-to
Content 
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)
History
Date User Action Args
2010-07-09 16:38:03amaury.forgeotdarcsetrecipients: + amaury.forgeotdarc, montulli, BreamoreBoy
2010-07-09 16:38:03amaury.forgeotdarcsetmessageid: <1278693483.37.0.975443660062.issue1147646@psf.upfronthosting.co.za>
2010-07-09 16:38:01amaury.forgeotdarclinkissue1147646 messages
2010-07-09 16:38:00amaury.forgeotdarccreate