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 gvanrossum
Recipients ajoino, alex.gronholm, asvetlov, chris.jerdonek, dreamsorcerer, gvanrossum, iritkatriel, jab, njs, serhiy.storchaka, tinchester, yselivanov
Date 2022-02-23.16:46:25
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1645634785.21.0.49189060105.issue46829@roundup.psfhosted.org>
In-reply-to
Content
But that example is made-up. Is there a real-world situation where you need to know the call site, and it wouldn't be obvious from other log messages?

Directly cancelling a task without also somehow catching the cancellation (like in the timeout or task group cases) feels like an odd practice to me.

And passing the cancel message through is complex (as we've seen in recent PRs).
History
Date User Action Args
2022-02-23 16:46:25gvanrossumsetrecipients: + gvanrossum, njs, jab, asvetlov, alex.gronholm, chris.jerdonek, serhiy.storchaka, yselivanov, tinchester, iritkatriel, dreamsorcerer, ajoino
2022-02-23 16:46:25gvanrossumsetmessageid: <1645634785.21.0.49189060105.issue46829@roundup.psfhosted.org>
2022-02-23 16:46:25gvanrossumlinkissue46829 messages
2022-02-23 16:46:25gvanrossumcreate