Re: Minimising stack trace

2015-05-16 Thread Cecil Westerhof
Op Friday 15 May 2015 20:17 CEST schreef Cecil Westerhof: > 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 th

Re: Minimising stack trace

2015-05-16 Thread Cecil Westerhof
Op Friday 15 May 2015 21:04 CEST schreef Ned Batchelder: > On Friday, May 15, 2015 at 2:50:12 PM UTC-4, 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

Re: Minimising stack trace

2015-05-15 Thread Mark Lawrence
On 16/05/2015 03:51, 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 recurs

Re: Minimising stack trace

2015-05-15 Thread Rustom Mody
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: > > > > > > >

Re: Minimising stack trace

2015-05-15 Thread Rustom Mody
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: > > >>

Re: Minimising stack trace

2015-05-15 Thread Ned Batchelder
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 > 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 wr

Re: Minimising stack trace

2015-05-15 Thread Chris Angelico
On Sat, May 16, 2015 at 11:24 AM, 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: maxi

Re: Minimising stack trace

2015-05-15 Thread Ned Batchelder
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

Re: Minimising stack trace

2015-05-15 Thread Steven D'Aprano
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 ‘

Re: Minimising stack trace

2015-05-15 Thread Thomas 'PointedEars' Lahn
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

Re: Minimising stack trace

2015-05-15 Thread Skip Montanaro
A third alternative is to take a look at asyncore.compact_traceback. That will only help modestly in Cecil's example, but I found it helpful. Skip On Fri, May 15, 2015 at 2:04 PM, Ned Batchelder wrote: > On Friday, May 15, 2015 at 2:50:12 PM UTC-4, Cecil Westerhof wrote: >> While playing with re

Re: Minimising stack trace

2015-05-15 Thread Ned Batchelder
On Friday, May 15, 2015 at 2:50:12 PM UTC-4, 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

Minimising stack trace

2015-05-15 Thread Cecil Westerhof
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. -- Cecil Westerhof Senior Softwar