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 alex.gronholm
Recipients ajoino, alex.gronholm, asvetlov, chris.jerdonek, gvanrossum, iritkatriel, jab, njs, tinchester, yselivanov
Date 2022-02-20.20:09:30
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1645387770.49.0.555862382259.issue46771@roundup.psfhosted.org>
In-reply-to
Content
> Alex, the 'scope' argument can be added if it is really required. 
> I'm not sure if the nonce is unavoidable still.

What other generic solution is there? I've read your last few messages but didn't find an answer. There needs to be some way to avoid a whole-task cancellation being ignored when it happens after a cancel scope triggers a cancellation for itself. My proposal solves that problem, and I think it eliminates the need for un-cancellation or other backwards incompatible changes.
History
Date User Action Args
2022-02-20 20:09:31alex.gronholmsetrecipients: + alex.gronholm, gvanrossum, njs, jab, asvetlov, chris.jerdonek, yselivanov, tinchester, iritkatriel, ajoino
2022-02-20 20:09:30alex.gronholmsetmessageid: <1645387770.49.0.555862382259.issue46771@roundup.psfhosted.org>
2022-02-20 20:09:30alex.gronholmlinkissue46771 messages
2022-02-20 20:09:30alex.gronholmcreate