Minimising stack trace

Rustom Mody rustompmody at gmail.com
Fri May 15 22:59:36 EDT 2015


On Saturday, May 16, 2015 at 8:22:05 AM UTC+5:30, Rustom Mody wrote:
> On Saturday, May 16, 2015 at 6:54:23 AM UTC+5:30, Ned Batchelder wrote:
> > On Friday, May 15, 2015 at 8:57:53 PM UTC-4, Steven D'Aprano wrote:
> > > On Sat, 16 May 2015 05:41 am, Thomas 'PointedEars' Lahn wrote:
> > > 
> > > > Cecil Westerhof wrote:
> > > > 
> > > >> While playing with recursion I get:
> > > >>     RuntimeError: maximum recursion depth exceeded in comparison
> > > >> 
> > > >> But then I get a very long stack trace. Is there a way to make this a
> > > >> lot shorter. Now I 'lose' interesting information because of the length
> > > >> of the stack trace.
> > > > 
> > > > <http://www.catb.org/~esr/faqs/smart-questions.html>
> > > 
> > > There ought to be a website that explains how to give smart answers.
> > 
> > Or one that explains how to be kind to those that don't know
> > the ropes yet.  Though pointing impatient experts at a
> > website probably won't get them to change any more than
> > brusquely pointing newbs at a website will.
> 
> How about a 'answerer-quota' 😇 ?
> 
> « Once for every 20 useful answers you are allowed to vent on any subject of 
>   your choice...
> 
>   - Stupid questions (and point to catb's smart questions)
>   - Google groups
>   - Top posting
>   - Html mail
> 
> »

Forgot the most important:   Using print's 😎



More information about the Python-list mailing list