Message 136004 - 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	neologix
Recipients	gregory.p.smith, nadeem.vawda, neologix, pitrou, sdaoden, vstinner
Date	2011-05-14.23:19:20
SpamBayes Score	7.1914417e-07
Marked as misclassified	No
Message-id	<1305415161.68.0.57058760488.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. Well, a pipe is 64K on Linux (4K on older kernels). Given that each signal received consumes one byte, I'd be pretty surprised if we managed to fill the pipe before Py_CheckSignals() gets called. > i think all of this is overkill. as said, this isn't a real problem. Definitely. Do you think this can be closed as "wont fix" ?

> 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.

Well, a pipe is 64K on Linux (4K on older kernels). Given that each signal received consumes one byte, I'd be pretty surprised if we managed to fill the pipe before Py_CheckSignals() gets called.

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

Definitely. Do you think this can be closed as "wont fix" ?

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