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 gvanrossum
Recipients achimnol, asvetlov, gvanrossum, yselivanov
Date 2022-02-24.17:02:17
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1645722137.2.0.439986473587.issue46844@roundup.psfhosted.org>
In-reply-to
Content
-1. Libraries that manage their own tasks should continue to do so, until they are ready to adopt TaskGroup. Trying to "own" (and wait for) tasks created by a library sounds like a recipe for disaster if the library wasn't expecting that.

Do you have a specific use case or scenario that has bitten you in the past? If you want to continue to argue for this feature we would need specifics (not a link to reams of code but a clear story telling of a problem you've encountered in real life in the past that your proposal might solve).
History
Date User Action Args
2022-02-24 17:02:17gvanrossumsetrecipients: + gvanrossum, asvetlov, yselivanov, achimnol
2022-02-24 17:02:17gvanrossumsetmessageid: <1645722137.2.0.439986473587.issue46844@roundup.psfhosted.org>
2022-02-24 17:02:17gvanrossumlinkissue46844 messages
2022-02-24 17:02:17gvanrossumcreate