Message 57055 - 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	schmir
Recipients	astrand, mattjohnston, mpitt, schmir, timjr
Date	2007-11-02.16:30:18
SpamBayes Score	0.23562415
Marked as misclassified	No
Message-id	<1194021018.99.0.869095776166.issue1068268@psf.upfronthosting.co.za>
In-reply-to

Content
In normal application code that signal.alarm is called for a reason. And the caller most probably expects it to interrupt the read calls. So I think the proposed patch is wrong. What was the signal interrupting the read calls? maybe SIGPIPE?

In normal application code that signal.alarm is called for a reason. And
the caller most probably expects it to interrupt the read calls. So I
think the proposed patch is wrong. 

What was the signal interrupting the read calls? maybe SIGPIPE?

History
Date	User	Action	Args
2007-11-02 16:30:19	schmir	set	spambayes_score: 0.235624 -> 0.23562415 recipients: + schmir, astrand, mattjohnston, mpitt, timjr
2007-11-02 16:30:19	schmir	set	spambayes_score: 0.235624 -> 0.235624 messageid: <1194021018.99.0.869095776166.issue1068268@psf.upfronthosting.co.za>
2007-11-02 16:30:18	schmir	link	issue1068268 messages
2007-11-02 16:30:18	schmir	create