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 Zhiping.Deng
Recipients Zhiping.Deng, neologix, terry.reedy, vstinner
Date 2011-06-04.13:12:38
SpamBayes Score 0.0009722393
Marked as misclassified No
Message-id <1307193158.73.0.684239047425.issue12224@psf.upfronthosting.co.za>
In-reply-to
Content
I think the problem is that after a user calles signal.siginterrupt(False), 
he would expect that the socket.recv should handles EINTR properly 
for him because it's the behaviour in c level. 
He doesn't know socket.recv() calles select(2) internally and he needn't.

Or at least this should be documented in signal.siginterrupt().
History
Date User Action Args
2011-06-04 13:12:38Zhiping.Dengsetrecipients: + Zhiping.Deng, terry.reedy, vstinner, neologix
2011-06-04 13:12:38Zhiping.Dengsetmessageid: <1307193158.73.0.684239047425.issue12224@psf.upfronthosting.co.za>
2011-06-04 13:12:38Zhiping.Denglinkissue12224 messages
2011-06-04 13:12:38Zhiping.Dengcreate