-
-
Notifications
You must be signed in to change notification settings - Fork 31.9k
GH-95289: Always call uncancel() when parent cancellation is requested #95602
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
8498dda
to
8cc90a5
Compare
We're getting very close to the RC1 release date (this Friday!). I'd like to get this in. @graingert can you bless this as strictly better than what we had before? |
I agree, I would like to get this in ASAP. |
This now follows the five (six? Cc @ambv) rules of uncancellation so I think therefore it's strictly better. However I can't say for sure. It looks to me like TaskGroup was relying on |
In addition I think there's other more fundamental problems with uncancel, for example when a cancellation is delivered from a chained concurrent.fututes.Future or when a TaskGroup task waits on another TaskGroup task and cancellation is chained between them |
Thanks @kumaraditya303 for the PR, and @gvanrossum for merging it 🌮🎉.. I'm working now to backport this PR to: 3.11. |
…quested (pythonGH-95602) Co-authored-by: Guido van Rossum <[email protected]> (cherry picked from commit 2fef275) Co-authored-by: Kumar Aditya <[email protected]>
GH-95654 is a backport of this pull request to the 3.11 branch. |
GH-95602) Co-authored-by: Guido van Rossum <[email protected]> (cherry picked from commit 2fef275) Co-authored-by: Kumar Aditya <[email protected]>
Co-Authored-By: Guido van Rossum [email protected]