Shorter tracebacks

rdmurray at bitdance.com rdmurray at bitdance.com
Sat Dec 13 15:33:36 CET 2008


On Sat, 13 Dec 2008 at 06:13, bearophileHUGS at lycos.com wrote:
> When I write recursive code in Python I sometimes go past the maximum
> allowed stack depth, so I receive a really long traceback. The show of
> such traceback on my screen is very slow (despite a CPU able to
> perform billions of operations each second). So I think I'd like
> something to shorten them.
> I am thinking about something like:
> from __future__ import short_traceback
>
> That allows me to see only the first and last parts of the stack
> trace, and skips the (generally very redundant) middle part.

_If_ such a feature were to be added, it should be a runtime option
to the interpreter, not a __future__ import.

--RDM



More information about the Python-list mailing list