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 asvetlov, gvanrossum, iritkatriel, njs, yselivanov
Date 2022-02-16.17:53:02
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1645033982.9.0.993216050351.issue46752@roundup.psfhosted.org>
In-reply-to
Content
@dhalbert, it's probably better to file a new issue if you want changes to gather(). Although I suppose that if we want to deemphasize it, we shouldn't be adding new features to it. My own new feature idea would be to have it wait for all tasks and then if there are any exceptions, raise an ExceptionGroup. That (like any new gather() behaviors) would require a new keyword-only flag to gather(). If we're going to deemphasize it I might not bother though.

There's one thing that gather() does that TaskGroup doesn't: it gives us the return values from the tasks. The question is whether that's useful. If it is maybe we should *not* deepmhasize gather() quite as much and then adding new features would be okay.
History
Date User Action Args
2022-02-16 17:53:02gvanrossumsetrecipients: + gvanrossum, njs, asvetlov, yselivanov, iritkatriel
2022-02-16 17:53:02gvanrossumsetmessageid: <1645033982.9.0.993216050351.issue46752@roundup.psfhosted.org>
2022-02-16 17:53:02gvanrossumlinkissue46752 messages
2022-02-16 17:53:02gvanrossumcreate