asyncio: Warning message when waiting for an Event set by AbstractLoop.add_reader

[Léo El Amri]

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 all the thing is behaving in the shadows. Maybe I'm
simply doing something wrong. But it would mean that the documentation
is lacking some details, or maybe that I'm just really stupid on this one.

On 03/08/2018 07:05, dieter wrote:
> Léo El Amri via Python-list <python-list at python.org> writes:
>> ...
>> WARNING:asyncio:Executing <Handle [CUT] locks.py:261> 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 guess.
>