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

STINNER Victor added the comment: Le lundi 29 juin 2015, Yury Selivanov a écrit : > > > > You should develop using asyncio debug mode: > > Maybe we should promote this check to the production mode? > asyncio must be slow. The check has a cost, I prefer to keep it only in debug mode. It's probab

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

Марк Коренберг added the comment: $ PYTHONASYNCIODEBUG=1 ./bug.py Starting busy receiver Busy receiver complete Executing wait_for= cb=[_run_until_complete_cb() at /usr/lib/python3.4/asyncio/base_events.py:123] created at /usr/lib/python3.4/asyncio/base_events.py:296> took 3.001 seconds Shoul

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

Марк Коренберг added the comment: Adding of b.setblocking(0) after socketpair() does not help. -- ___ Python tracker ___ ___ Python-bu

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

Yury Selivanov added the comment: > You should develop using asyncio debug mode: Maybe we should promote this check to the production mode? -- ___ Python tracker ___ ___

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

STINNER Victor added the comment: You should develop using asyncio debug mode: https://docs.python.org/dev/library/asyncio-dev.html#asyncio-dev haypo@selma$ PYTHONASYNCIODEBUG=1 ./python x.py Starting busy receiver Traceback (most recent call last): File "x.py", line 21, in main() Fil

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

New submission from Марк Коренберг: Suppose that program: import asyncio import socket def receiver(loop): (a, b) = socket.socketpair() loop.call_later(1, lambda: print('Should be called inside the loop')) end = loop.time() + 3 print('Starting