In my previous article (Server-oriented task scope design - #2 by achimnol), I’ve suggested to have a nested tree of “task scope” (or “supervisor scope”) for an asyncio server application. One of the core idea is to be able to consume the unhandled exceptions in a hierarchical manner, instead of relying on the global loop.set_exception_handler().
Without impacting existing asyncio applications, I think we could reconsider the concept of nested task scopes.