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 Jerzy.Kozera
Recipients Christophe Simonis, Jerzy.Kozera, Yaniv.Aknin, bda, exarkun, giampaolo.rodola, gregory.p.smith, kchen, neologix, nvetoshkin, pitrou, python-dev, spiv, vstinner
Date 2012-04-08.23:38:42
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1333928323.52.0.929484286867.issue7978@psf.upfronthosting.co.za>
In-reply-to
Content
I forgot to mention my patch is 3.3-only, sorry - it depends on changes from #12555 (http://hg.python.org/cpython/rev/41a1de81ef2b#l18.21 to be precise). To support 3.2 and 2.7:
 (1) select.error must be caught as in the original patch,
 (2) e.args[0] must be used - select.error doesn't have 'errno' attribute.
Should I prepare the patch for 3.2 and 2.7?

Regarding not updating the timeout, it was already mentioned above. Though as an afterthought, it might be worrying that if the process is receiving repeated signals with interval between them less than timeout, we might fall into infinite loop of select() when it should timeout, but that is probably very obscure case.
History
Date User Action Args
2012-04-08 23:38:43Jerzy.Kozerasetrecipients: + Jerzy.Kozera, gregory.p.smith, spiv, exarkun, pitrou, vstinner, giampaolo.rodola, Christophe Simonis, nvetoshkin, neologix, Yaniv.Aknin, bda, kchen, python-dev
2012-04-08 23:38:43Jerzy.Kozerasetmessageid: <1333928323.52.0.929484286867.issue7978@psf.upfronthosting.co.za>
2012-04-08 23:38:42Jerzy.Kozeralinkissue7978 messages
2012-04-08 23:38:42Jerzy.Kozeracreate