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 yselivanov
Recipients chris.jerdonek, matrixise, socketpair, thehesiod, yselivanov
Date 2018-04-04.22:04:42
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1522879482.73.0.682650639539.issue31033@psf.upfronthosting.co.za>
In-reply-to
Content
> I like the idea of having an argument to construct the CancelledError with, but I like even more the ability to tell the exception that will be raised to have the traceback of the point where the task was originally cancelled.

Why don't we make CancelledErrors having proper traceback a default behaviour?
History
Date User Action Args
2018-04-04 22:04:42yselivanovsetrecipients: + yselivanov, chris.jerdonek, socketpair, matrixise, thehesiod
2018-04-04 22:04:42yselivanovsetmessageid: <1522879482.73.0.682650639539.issue31033@psf.upfronthosting.co.za>
2018-04-04 22:04:42yselivanovlinkissue31033 messages
2018-04-04 22:04:42yselivanovcreate