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 pitrou
Recipients asvetlov, njs, pitrou, vstinner, yselivanov
Date 2017-12-19.16:10:04
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1513699804.9.0.213398074469.issue32373@psf.upfronthosting.co.za>
In-reply-to
Content
> Now is having a timeout and blocking send/recv methods on a non-blocking socket a feature? Or is this a bug?

I agree it's a bug (but should only be fixed in 3.7).

Also I agree with adding a socket.getblocking() method.
History
Date User Action Args
2017-12-19 16:10:04pitrousetrecipients: + pitrou, vstinner, njs, asvetlov, yselivanov
2017-12-19 16:10:04pitrousetmessageid: <1513699804.9.0.213398074469.issue32373@psf.upfronthosting.co.za>
2017-12-19 16:10:04pitroulinkissue32373 messages
2017-12-19 16:10:04pitroucreate