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 pagliaricci.m
Recipients asvetlov, bjs, chris.jerdonek, graingert, pagliaricci.m, yselivanov
Date 2022-02-17.09:37:54
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAHWeiQUPJQEJuqkodinh4rECvCv0h7qiEro0KLqfyNFo9DUJcQ@mail.gmail.com>
In-reply-to <1645090017.54.0.598598572151.issue45390@roundup.psfhosted.org>
Content
Andrew,
many thanks for your time, solving this issue.
I think your solution is the best to fix this little problem and I agree
with you on backporting.

My Best Regards,
and thanks again.

Marco

On Thu, Feb 17, 2022 at 10:29 AM Andrew Svetlov <report@bugs.python.org>
wrote:

>
> Andrew Svetlov <andrew.svetlov@gmail.com> added the comment:
>
> 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.
>
> ----------
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <https://bugs.python.org/issue45390>
> _______________________________________
>
History
Date User Action Args
2022-02-17 09:37:54pagliaricci.msetrecipients: + pagliaricci.m, asvetlov, chris.jerdonek, yselivanov, graingert, bjs
2022-02-17 09:37:54pagliaricci.mlinkissue45390 messages
2022-02-17 09:37:54pagliaricci.mcreate