Message 55926 - Python tracker

➜

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	arigo
Recipients	arigo, brett.cannon
Date	2007-09-15.08:30:10
SpamBayes Score	0.12161977
Marked as misclassified	No
Message-id	<1189845012.18.0.975747896195.issue1164@psf.upfronthosting.co.za>
In-reply-to

Content
We need to start from PyFile_WriteString() and PyFile_WriteObject() and PyObject_Print(), which are what the PRINT_* opcodes use, and make sure there is no single fprintf() or fputs() that occurs with the GIL held. It is not enough to fix a few places that could clearly write a lot of data, because even if there is just one place left where the GIL is not released it could be precisely where the OS decides to block, causing a deadlock.

We need to start from PyFile_WriteString() and PyFile_WriteObject()
and PyObject_Print(), which are what the PRINT_* opcodes use, and make
sure there is no single fprintf() or fputs() that occurs with the GIL
held.  It is not enough to fix a few places that could clearly write a
lot of data, because even if there is just one place left where the GIL
is not released it could be precisely where the OS decides to block,
causing a deadlock.

History
Date	User	Action	Args
2007-09-15 08:30:12	arigo	set	spambayes_score: 0.12162 -> 0.12161977 recipients: + arigo, brett.cannon
2007-09-15 08:30:12	arigo	set	spambayes_score: 0.12162 -> 0.12162 messageid: <1189845012.18.0.975747896195.issue1164@psf.upfronthosting.co.za>
2007-09-15 08:30:12	arigo	link	issue1164 messages
2007-09-15 08:30:10	arigo	create