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 izbyshev
Recipients abacabadabacaba, anacrolix, benjamin.peterson, docs@python, izbyshev, martin.panter, neologix, pitrou, python-dev, sbt, stutzbach
Date 2017-12-06.21:14:39
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Yes, your claim is confirmed by the fact that there have been little interest in this issue since 2011. Still, non-blocking behavior is incorrectly specified in the docs and is inconsistent (as investigated by Martin). And obscure errors like in my example or in Issue 13858 show that I/O stack is confused too. To prevent people from tripping on it, would you consider recommending against usage of I/O stack for non-blocking operations in io module docs?
Date User Action Args
2017-12-06 21:14:40izbyshevsetrecipients: + izbyshev, pitrou, benjamin.peterson, stutzbach, anacrolix, neologix, abacabadabacaba, docs@python, python-dev, sbt, martin.panter
2017-12-06 21:14:40izbyshevsetmessageid: <>
2017-12-06 21:14:39izbyshevlinkissue13322 messages
2017-12-06 21:14:39izbyshevcreate