Message307770
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:40 | izbyshev | set | recipients:
+ izbyshev, pitrou, benjamin.peterson, stutzbach, anacrolix, neologix, abacabadabacaba, docs@python, python-dev, sbt, martin.panter |
2017-12-06 21:14:40 | izbyshev | set | messageid: <1512594880.0.0.213398074469.issue13322@psf.upfronthosting.co.za> |
2017-12-06 21:14:39 | izbyshev | link | issue13322 messages |
2017-12-06 21:14:39 | izbyshev | create | |
|