Message413964
I have added more about my stories in bpo-46843.
I think the suggestion of implicit taskgroup binding with the current asyncio.TaskGroup has no point but it would have more meaning with PersistentTaskGroup.
So, if we treat PersistentTaskGroup as a "nested, hierarchical virtual event loop" to repeat and group shutdown procedures for different task sets separately, the point may look a little bit clearer.
It is more like assigning a virtual event loop to different modules and libraries, while keeping the behavior of asyncio.create_task() same. The difference is that the caller controls when these virtual loops are terminated and in what order.
Does this make sense better? |
|
Date |
User |
Action |
Args |
2022-02-25 05:23:27 | achimnol | set | recipients:
+ achimnol, gvanrossum, asvetlov, yselivanov |
2022-02-25 05:23:27 | achimnol | set | messageid: <1645766607.05.0.16586507729.issue46844@roundup.psfhosted.org> |
2022-02-25 05:23:27 | achimnol | link | issue46844 messages |
2022-02-25 05:23:26 | achimnol | create | |
|