I've got to say, I've never actually noticed a problem with "fire and forget" although I use it for more or less disposable tasks to begin with. However, I've

I've got to say, I've never actually noticed a problem with "fire and forget" although I use it for more or less disposable tasks to begin with. However, I've spent some more time looking through asyncio.base_events and * BaseEventLoop._scheduled is a list() * BaseEventLoop._ready is a deque() There is no change between 3.6 and 3.11 in this regard. So this could be a nothingburger if you don't use asyncgens. OTOH I suppose better safe than sorry; the only question is whether no code addressing it is more mentally taxing for the bystander than having code and trusting its implementation.