➜

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 JohannesEbke, MartinAltmayer, gvanrossum, tatellos, vstinner, yselivanov
Date 2016-06-15.00:55:13
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1465952115.12.0.805795024729.issue26923@psf.upfronthosting.co.za>
In-reply-to
Content 
I think I agree with Johannes. If all children refuse to be cancelled because they are already done, the outer _GatheringFuture might as well refuse to be cancelled as well.

However I'm not sure I actually understand the mechanism whereby the calling Task ends up surviving, and Johannes' description appears garbled.

Can anyone add some print statements to various parts and explain it here?
History
Date User Action Args
2016-06-15 00:55:15gvanrossumsetrecipients: + gvanrossum, vstinner, MartinAltmayer, yselivanov, JohannesEbke, tatellos
2016-06-15 00:55:15gvanrossumsetmessageid: <1465952115.12.0.805795024729.issue26923@psf.upfronthosting.co.za>
2016-06-15 00:55:15gvanrossumlinkissue26923 messages
2016-06-15 00:55:14gvanrossumcreate