I found out what was the problem.
The behavior of my "reader" (The callback passed to
AbstractEventLoop.add_reader()) is to set an event. This event is
awaited for in a coroutine which actually reads what is written on a
pipe. The execution flow is the following:
* NEW LOOP TURN
* The selector aw
Thanks for the answer, but the problem is that this is happening in the
built-in Event of the asyncio package; which is actually a coroutine. I
don't expect the built-in to have this kind of behavior. I guess I'll
have to dig on the source code of the asyncio default loop to actually
understand how
Léo El Amri via Python-list writes:
> ...
> WARNING:asyncio:Executing took 1.000 seconds
> ...
> But there is still this warning...
At your place, I would look at the code responsible for the warning.
I assume that it is produced because the waiting time is rather
high -- but this is just a gue
Hello list,
During my attempt to bring asyncio support to the multiprocessing Queue,
I found warning messages when executing my code with asyncio debug
logging enabled.
It seems that awaiting for an Event will make theses messages appears
after the second attempt to wait for the Event.
Here is a
