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, lilydjwg, yselivanov
Date 2020-12-23.10:40:52
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
The traceback contains frames from asyncio internal machinery, that's why the traceback is long.

IFIAK Python standard library never filters such calls, asyncio is not an exception.

On the other hand, well-known pytest library supports `__tracebackhide__ = True` for skipping pytest internals in test failure reports.
I'm not sure if we want to do such black magic though.

Plus, sometimes an information about internals is helpful to detect the actual source of the problem,

I have no clear vision of how to skip internal frames easily. 

Yuri, maybe you have an idea?
Date User Action Args
2020-12-23 10:40:52asvetlovsetrecipients: + asvetlov, lilydjwg, yselivanov
2020-12-23 10:40:52asvetlovsetmessageid: <>
2020-12-23 10:40:52asvetlovlinkissue42682 messages
2020-12-23 10:40:52asvetlovcreate