Message 413392 - Python tracker

➜

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	asvetlov
Recipients	asvetlov, bjs, chris.jerdonek, graingert, pagliaricci.m, yselivanov
Date	2022-02-17.09:26:57
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1645090017.54.0.598598572151.issue45390@roundup.psfhosted.org>
In-reply-to

Content
I have a pull request for the issue. It doesn't use `Future.set_exception()` but creates a new CancelledError() with propagated message. The result is the same, except raised exceptions are not comparable by `is` check. As a benefit, `_cancelled_exc` works with the patch, exc.__context__ is correctly set. The patch is not backported because it changes existing behavior a little. I'd like to avoid a situation when third-party code works with Python 3.11+, 3.10.3+, and 3.9.11+ only.

I have a pull request for the issue.
It doesn't use `Future.set_exception()` but creates a new CancelledError() with propagated message.
The result is the same, except raised exceptions are not comparable by `is` check.
As a benefit, `_cancelled_exc` works with the patch, exc.__context__ is correctly set.

The patch is not backported because it changes existing behavior a little. I'd like to avoid a situation when third-party code works with Python 3.11+, 3.10.3+, and 3.9.11+ only.

History
Date	User	Action	Args
2022-02-17 09:26:57	asvetlov	set	recipients: + asvetlov, chris.jerdonek, yselivanov, graingert, bjs, pagliaricci.m
2022-02-17 09:26:57	asvetlov	set	messageid: <1645090017.54.0.598598572151.issue45390@roundup.psfhosted.org>
2022-02-17 09:26:57	asvetlov	link	issue45390 messages
2022-02-17 09:26:57	asvetlov	create