Message 135012 - 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	pitrou
Recipients	bobbyi, gregory.p.smith, neologix, pitrou
Date	2011-05-03.00:20:59
SpamBayes Score	5.0333074e-07
Marked as misclassified	No
Message-id	<1304382060.39.0.743272224243.issue6721@psf.upfronthosting.co.za>
In-reply-to

Content
I encountered this issue while debugging some multiprocessing code; fork() would be called from one thread while sys.stdout was in use in another thread (simply because of a couple of debugging statements). As a result the IO lock would be already "taken" in the child process and any operation on sys.stdout would deadlock. This is definitely something that can happen more easily than I thought.

I encountered this issue while debugging some multiprocessing code; fork() would be called from one thread while sys.stdout was in use in another thread (simply because of a couple of debugging statements). As a result the IO lock would be already "taken" in the child process and any operation on sys.stdout would deadlock.

This is definitely something that can happen more easily than I thought.

History
Date	User	Action	Args
2011-05-03 00:21:00	pitrou	set	recipients: + pitrou, gregory.p.smith, bobbyi, neologix
2011-05-03 00:21:00	pitrou	set	messageid: <1304382060.39.0.743272224243.issue6721@psf.upfronthosting.co.za>
2011-05-03 00:20:59	pitrou	link	issue6721 messages
2011-05-03 00:20:59	pitrou	create