➜

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, dreamsorcerer, gvanrossum, iritkatriel, jab, njs, tinchester, yselivanov
Date 2022-02-21.00:05:23
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1645401923.59.0.890374370257.issue46771@roundup.psfhosted.org>
In-reply-to
Content 
> Propagating an ExceptionGroup where every exception can be inspected to see if it was caused by this code or not still seems like the safe option to me (and obviously still has the cancel count implicitly).

Note that this, too, causes backwards incompatible changes in cancellation behavior. Previously, when the task was cancelled twice, only one CancelledError was raised. Now it would raise a BaseExceptionGroup instead.

The current backward incompatible changes in cancellation behavior are already causing 10 tests to fail in the AnyIO test suite. I'm trying to find an alternate solution that does not break anything.
History
Date User Action Args
2022-02-21 00:05:23alex.gronholmsetrecipients: + alex.gronholm, gvanrossum, njs, jab, asvetlov, chris.jerdonek, yselivanov, tinchester, iritkatriel, dreamsorcerer, ajoino
2022-02-21 00:05:23alex.gronholmsetmessageid: <1645401923.59.0.890374370257.issue46771@roundup.psfhosted.org>
2022-02-21 00:05:23alex.gronholmlinkissue46771 messages
2022-02-21 00:05:23alex.gronholmcreate