Andrew Svetlov <andrew.svet...@gmail.com> added the comment:
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? ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue42682> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
