This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author achimnol
Recipients achimnol, asvetlov, gvanrossum, yselivanov
Date 2022-02-24.13:33:16
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1645709596.75.0.207334976218.issue46843@roundup.psfhosted.org>
In-reply-to
Content
I think people may ask "why in stdlib?".

My reasons are:
 - We are adding new asyncio APIs in 3.11 such as TaskGroup, so I think it is a good time to add another one, as long as it does not break existing stuffs.
 - I believe that long-running task sets are equally representative use-case for real-world asyncio applications, particularly for servers.  Why not to have intrinsic support for them?
 - PersistentTaskGroup is going to be universally adopted throughout my 70+K LoC asyncio codebase, for instance, in every aiohttp.Application context, plugin contexts and modules, etc.

Of course, the name "PersistentTaskGroup" may look quite long, and I'm completely open with alternative suggestions.  I also welcome suggestions on changes to its functional semantics based on your experience and knowledge.
History
Date User Action Args
2022-02-24 13:33:16achimnolsetrecipients: + achimnol, gvanrossum, asvetlov, yselivanov
2022-02-24 13:33:16achimnolsetmessageid: <1645709596.75.0.207334976218.issue46843@roundup.psfhosted.org>
2022-02-24 13:33:16achimnollinkissue46843 messages
2022-02-24 13:33:16achimnolcreate