➜

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 amaury.forgeotdarc, docs@python, georg.brandl, glchapman21, kunoospald, terry.reedy, urBan_dK
Date 2010-07-10.07:36:33
SpamBayes Score 0.001030654
Marked as misclassified No
Message-id <1278747397.02.0.173500361676.issue1720250@psf.upfronthosting.co.za>
In-reply-to
Content 
This is still the case: the documentation should mention that PyEval_ReleaseLock() is not the correct function to release "the GIL", both the interpreter lock *and* the current thread state have to be released.
History
Date User Action Args
2010-07-10 07:36:37amaury.forgeotdarcsetrecipients: + amaury.forgeotdarc, georg.brandl, terry.reedy, kunoospald, urBan_dK, glchapman21, docs@python
2010-07-10 07:36:37amaury.forgeotdarcsetmessageid: <1278747397.02.0.173500361676.issue1720250@psf.upfronthosting.co.za>
2010-07-10 07:36:34amaury.forgeotdarclinkissue1720250 messages
2010-07-10 07:36:34amaury.forgeotdarccreate