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 JelleZijlstra
Recipients JelleZijlstra, gvanrossum, iritkatriel
Date 2022-03-07.16:52:16
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1646671936.93.0.679667824145.issue46949@roundup.psfhosted.org>
In-reply-to
Content
If the number of frames in a traceback exceeds sys.tracebacklimit (which defaults to 1000), any remaining frames are silently dropped. See https://docs.python.org/3.10/library/sys.html#sys.tracebacklimit.

This is confusing to users. We should print some indication like "N additional stack frames not shown".

Here are some specific ideas:
- tracebacklimit <= 0 is documented as dropping the whole traceback. In that case, we don't need too print any message.
- It may be expensive to compute a complete count. Perhaps we can count frames up to 2 * tracebacklimit, and just say "Many additional stack frames not shown".
- The C implementation is in tb_print_internal() in traceback.c, and the Python one in _extract_from_extended_frame_gen in traceback.py.
History
Date User Action Args
2022-03-07 16:52:16JelleZijlstrasetrecipients: + JelleZijlstra, gvanrossum, iritkatriel
2022-03-07 16:52:16JelleZijlstrasetmessageid: <1646671936.93.0.679667824145.issue46949@roundup.psfhosted.org>
2022-03-07 16:52:16JelleZijlstralinkissue46949 messages
2022-03-07 16:52:16JelleZijlstracreate