On Fri, Jan 29, 2010 at 08:02:58PM -0500, P.J. Eby wrote:
> At 01:24 AM 1/30/2010 +0100, Ludvig Ericson wrote:
>
>> On 28 jan 2010, at 22:47, P.J. Eby wrote:
>>
>> > At 07:47 PM 1/28/2010 +0100, Benjamin Schweizer wrote:
>> >>
>> >> I like the ide
Hello pje,
On Thu, Jan 28, 2010 at 12:43:13PM -0500, P.J. Eby wrote:
> At 11:01 AM 1/28/2010 -0600, s...@pobox.com wrote:
>
>> pje> If you look for a local variable in each frame containing a format
>> pje> string, let's say __trace__, you could apply that format string to
>> pje> a lo
Hi Guido,
On Thu, Jan 28, 2010 at 5:02 PM, Guido van Rossum wrote:
> On Thu, Jan 28, 2010 at 5:33 AM, Benjamin Schweizer
> wrote:
> > I've updated the traceback.py module; my improved version dumps all
> > local variabes from the stack trace, which helps in debugging rar
Hi Kristján,
I have a traceback2.py module with the same api as traceback. Displaying
> local variables is optional through keyword arguments.
> I was also able to refactor the original significantly, making it much
> clearer.
>
traceback2.py was my first attempt; but I finally came out with a p
Hello Facuno,
I would love to get tracebacks with all variables in all levels of the
> stack.
>
> However, this may be too much information for standard tracebacks, so
> what do you think to enable it on demand? Like setting a flag or
> importing a module at the beginning of the file?
>
I've adde
Hello,
I've updated the traceback.py module; my improved version dumps all
local variabes from the stack trace, which helps in debugging rare
problems. You can find details in my latest blog post here:
http://benjamin-schweizer.de/improved-python-traceback-module.html
and the source code there
