Andrew Borba added the comment:
> The key word here is "misbehaving". Cooperative concurrency does require
> cooperation.
Your stance makes sense in an ideal environment where we control every Task
that our application deals with. However, there are some cases in which busted
Task
Caleb Hattingh added the comment:
> asyncio.wait_for is still confusing
Perhaps the confusion can be fixed with improvements to the docs? To me, these
specific docs seem pretty clear now, but I might not be a good judge of that.
> However, we still have the case where a misbehaving Task can
New submission from David Lewis :
This issue is a follow up to previous discussions about confusing results with
asyncio.wait_for. In the current implementation, it seems unintuitive that a
coroutine with a timeout argument may easily wait forever. Perhaps wait_for
could use an
