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 Jim.Jewett
Recipients Jim.Jewett, asksol, jnoller, ryles, underrun
Date 2012-01-25.22:55:27
SpamBayes Score 5.0834e-09
Marked as misclassified No
Message-id <>
The wording in 138415 suggested this patch was changing socket to not support timeouts -- which would be unacceptable.  

But the actual patch only seems to touch multiprocessing/ -- a far more reasonable change.

Unfortunately, the patch no longer applies to the development tip.  I *think* the places you wanted to change are still there, and just moved.

(1)  Is it sufficiently clear that this is not-a-feature to justify a backport?

(2)  Are the problems already fixed by some of the other changes?  (It doesn't look like it, but I'm not sure.)

(3)  Can you produce an updated patch?  (The current tip is  )

(4)  If I understand the intent, then s.setblocking(True) would be slightly more clear than s.settimeout(None), though that change obviously isn't essential.
Date User Action Args
2012-01-25 22:55:28Jim.Jewettsetrecipients: + Jim.Jewett, jnoller, ryles, asksol, underrun
2012-01-25 22:55:28Jim.Jewettsetmessageid: <>
2012-01-25 22:55:28Jim.Jewettlinkissue6056 messages
2012-01-25 22:55:27Jim.Jewettcreate