Re: plpython tracebacks - Mailing list pgsql-patches

From daveg
Subject Re: plpython tracebacks
Date
Msg-id 20060220072045.GE9992@sonic.net
Whole thread Raw
In response to Re: plpython tracebacks  (Neil Conway <neilc@samurai.com>)
List pgsql-patches
On Sun, Feb 19, 2006 at 08:09:09PM -0500, Neil Conway wrote:
> On Mon, 2006-02-06 at 16:05 -0600, P. Scott DeVos wrote:
> > I have been working with plpython for several months and have
> > been hampered by the lack of a traceback being logged when a
> > plpython function raises an error.  I have written a patch causes
> > the PLy_traceback function to fully log the traceback.  The
> > output looks just like the traceback output provided by the
> > python interpreter.
>
> Can any PL/Python folks comment on whether they want this patch?

Yes. Absolutely. This is a required feature for any serious Python user.

One of the great things about python is that almost all debugging can be
done with just the excellent standard python tracebacks. Not having them is a
a not only a inconvience, it signals that the implementation is incomplete
in major ways and, unready for real use.

-dg

--
David Gould                      daveg@sonic.net
If simplicity worked, the world would be overrun with insects.

pgsql-patches by date:

Previous
From: "Harald Armin Massa"
Date:
Subject: Re: plpython tracebacks
Next
From: Martijn van Oosterhout
Date:
Subject: [PATCH] WIP: Create shell-types explicitly