[issue24532] asyncio.sock_recv() blocks normal ioloop actions.

[STINNER Victor]

STINNER Victor added the comment:

You should develop using asyncio debug mode:

https://docs.python.org/dev/library/asyncio-dev.html#asyncio-dev

haypo at selma$ PYTHONASYNCIODEBUG=1 ./python x.py 
Starting busy receiver
Traceback (most recent call last):
  File "x.py", line 21, in <module>
    main()
  File "x.py", line 18, in main
    loop.run_until_complete(receiver(loop))
  File "/home/haypo/prog/python/default/Lib/asyncio/base_events.py", line 341, in run_until_complete
    return future.result()
  File "/home/haypo/prog/python/default/Lib/asyncio/futures.py", line 276, in result
    raise self._exception
  File "/home/haypo/prog/python/default/Lib/asyncio/tasks.py", line 238, in _step
    result = coro.send(value)
  File "x.py", line 11, in receiver
    yield from loop.sock_recv(b, 65536)
  File "/home/haypo/prog/python/default/Lib/asyncio/selector_events.py", line 316, in sock_recv
    raise ValueError("the socket must be non-blocking")
ValueError: the socket must be non-blocking
/home/haypo/prog/python/default/Lib/asyncio/base_events.py:384: ResourceWarning: unclosed event loop <_UnixSelectorEventLoop running=False closed=False debug=True>
sys:1: ResourceWarning: unclosed <socket object at 0x7f0b03d7d688>
sys:1: ResourceWarning: unclosed <socket object at 0x7f0b03d7d5f8>

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue24532>
_______________________________________