Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #90708

Re: Minimising stack trace

Newsgroups comp.lang.python
Date 2015-05-15 18:37 -0700
References <871tih66z5.fsf@Equus.decebal.nl> <1585804.vCLx6kbzfH@PointedEars.de> <55569607$0$13008$c3e8da3$5496439d@news.astraweb.com> <9cbf3b8e-e830-46f5-a636-27c0d07f460a@googlegroups.com> <mailman.55.1431739994.17265.python-list@python.org>
Message-ID <b644d3ca-58cc-4dd6-adaa-c9cc73ec39dd@googlegroups.com> (permalink)
Subject Re: Minimising stack trace
From Ned Batchelder <ned@nedbatchelder.com>

Show all headers | View raw


On Friday, May 15, 2015 at 9:33:54 PM UTC-4, Chris Angelico wrote:
> On Sat, May 16, 2015 at 11:24 AM, Ned Batchelder <ned@nedbatchelder.com> 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.
> 
> You mean like this?
> 
> http://www.catb.org/~esr/faqs/smart-questions.html#idp64834912
> 
> (Not sure whether you knew and were hinting, or didn't know that
> that's explicitly mentioned.)

I didn't realize that was in there. :) It's a good demonstration
that we can all improve in various ways.  Being right isn't the
highest ideal, there are other things to aspire to as well.

--Ned.

Back to comp.lang.python | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

Minimising stack trace Cecil Westerhof <Cecil@decebal.nl> - 2015-05-15 20:17 +0200
  Re: Minimising stack trace Ned Batchelder <ned@nedbatchelder.com> - 2015-05-15 12:04 -0700
    Re: Minimising stack trace Skip Montanaro <skip.montanaro@gmail.com> - 2015-05-15 14:14 -0500
    Re: Minimising stack trace Cecil Westerhof <Cecil@decebal.nl> - 2015-05-16 09:22 +0200
  Re: Minimising stack trace Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2015-05-15 21:41 +0200
    Re: Minimising stack trace Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2015-05-16 10:57 +1000
      Re: Minimising stack trace Ned Batchelder <ned@nedbatchelder.com> - 2015-05-15 18:24 -0700
        Re: Minimising stack trace Chris Angelico <rosuav@gmail.com> - 2015-05-16 11:33 +1000
          Re: Minimising stack trace Ned Batchelder <ned@nedbatchelder.com> - 2015-05-15 18:37 -0700
        Re: Minimising stack trace Rustom Mody <rustompmody@gmail.com> - 2015-05-15 19:51 -0700
          Re: Minimising stack trace Rustom Mody <rustompmody@gmail.com> - 2015-05-15 19:59 -0700
          Re: Minimising stack trace Mark Lawrence <breamoreboy@yahoo.co.uk> - 2015-05-16 04:49 +0100
  Re: Minimising stack trace Cecil Westerhof <Cecil@decebal.nl> - 2015-05-16 15:49 +0200

csiph-web