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 yselivanov
Recipients Andrew Lytvyn, asvetlov, gvanrossum, kwarunek, yselivanov
Date 2017-09-22.04:36:42
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> I'm afraid I no longer have all the details of this design in my head, and I have no idea what the fix does (and no time to read up on everything).

Let's say we have three tasks: t1, t2, t3.  Then we use gather on them:

   await gather(t1, t2, t3)

Let's say that t2 finishes first with an exception.

Currently, both t1 and t3 would continue their execution even though gather throws the t2 exception.

The PR for this issue makes 'gather' to cancel both t1 and t3 as soon as t2 throws an exception.

The question is: I see the point of the PR, but I'm afraid that it's too late to change the semantics of asyncio.gather.  Instead we should consider adding new TaskGroup API (we discussed it briefly on the sprint).
Date User Action Args
2017-09-22 04:36:42yselivanovsetrecipients: + yselivanov, gvanrossum, asvetlov, kwarunek, Andrew Lytvyn
2017-09-22 04:36:42yselivanovsetmessageid: <>
2017-09-22 04:36:42yselivanovlinkissue31452 messages
2017-09-22 04:36:42yselivanovcreate