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 abacabadabacaba, anacrolix, benjamin.peterson, docs@python, izbyshev, martin.panter, neologix, pitrou, python-dev, sbt, stutzbach
Date 2017-12-06.18:57:04
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1512586624.32.0.213398074469.issue13322@psf.upfronthosting.co.za>
In-reply-to
Content
Generally I doubt anyone is using the non-blocking semantics of the Python 3 I/O stack.  People doing non-blocking I/O generally do it with sockets instead, which tend to reproduce quite literally the POSIX behaviour and error codes.
History
Date User Action Args
2017-12-06 18:57:04pitrousetrecipients: + pitrou, benjamin.peterson, stutzbach, anacrolix, neologix, abacabadabacaba, docs@python, python-dev, sbt, martin.panter, izbyshev
2017-12-06 18:57:04pitrousetmessageid: <1512586624.32.0.213398074469.issue13322@psf.upfronthosting.co.za>
2017-12-06 18:57:04pitroulinkissue13322 messages
2017-12-06 18:57:04pitroucreate