Re: plpython tracebacks

From: daveg <daveg(at)sonic(dot)net>
To: Neil Conway <neilc(at)samurai(dot)com>
Cc: "P(dot) Scott DeVos" <scott(at)countrysidetechnology(dot)com>, pgsql-patches(at)postgresql(dot)org
Subject: Re: plpython tracebacks
Date: 2006-02-20 07:20:45
Message-ID: 20060220072045.GE9992@sonic.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)sonic(dot)net
If simplicity worked, the world would be overrun with insects.

In response to

Browse pgsql-patches by date

  From Date Subject
Next Message Milorad Poluga 2006-02-20 08:39:27 Re: Interval subtracting
Previous Message Harald Armin Massa 2006-02-20 05:14:22 Re: plpython tracebacks