Message 136001 - 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	gregory.p.smith
Recipients	gregory.p.smith, nadeem.vawda, neologix, pitrou, sdaoden, vstinner
Date	2011-05-14.22:49:05
SpamBayes Score	3.082926e-05
Marked as misclassified	No
Message-id	<1305413346.36.0.506947175138.issue12060@psf.upfronthosting.co.za>
In-reply-to

Content
if you used the pipe approach you'd need to deal with the case of the write blocking (or failing if nonblocking) when the pipe buffer is full. also you'd need to block signals around a fork and reinitialize the pipe in the child before reenabling signals. i think all of this is overkill. as said, this isn't a real problem.

if you used the pipe approach you'd need to deal with the case of the write blocking (or failing if nonblocking) when the pipe buffer is full.  also you'd need to block signals around a fork and reinitialize the pipe in the child before reenabling signals.

i think all of this is overkill.  as said, this isn't a real problem.

History
Date	User	Action	Args
2011-05-14 22:49:06	gregory.p.smith	set	recipients: + gregory.p.smith, pitrou, vstinner, nadeem.vawda, neologix, sdaoden
2011-05-14 22:49:06	gregory.p.smith	set	messageid: <1305413346.36.0.506947175138.issue12060@psf.upfronthosting.co.za>
2011-05-14 22:49:05	gregory.p.smith	link	issue12060 messages
2011-05-14 22:49:05	gregory.p.smith	create