Re: plpython3

Bruce Momjian <bruce@momjian.us>

From: Bruce Momjian <bruce@momjian.us>
To: Alvaro Herrera <alvherre@commandprompt.com>
Cc: Peter Eisentraut <peter_e@gmx.net>, Nathan Boley <npboley@gmail.com>, Robert Haas <robertmhaas@gmail.com>, James William Pye <lists@jwp.name>, Greg Smith <greg@2ndquadrant.com>, jd@commandprompt.com, Josh Berkus <josh@agliodbs.com>, PostgreSQL-development Hackers <pgsql-hackers@postgresql.org>
Date: 2010-02-01T21:13:39Z
Lists: pgsql-hackers
Alvaro Herrera wrote:
> Peter Eisentraut escribi?:
> > On m?n, 2010-02-01 at 12:01 -0800, Nathan Boley wrote:
> > > I code nearly exclusively in python and C, but I have
> > > often found pl/python to be very unwieldy.  For this reason I often
> > > use pl/perl or pl/pgsql for problems that, outside of postgres, I
> > > would always use python.
> > 
> > I find that curious, because much of the criticism about the current
> > PL/Python can be traced back to the fact that the implementation used to
> > be an exact copy of PL/Perl.
> 
> Perhaps the problem is that PL/Perl used to be unwieldy back when
> PL/Python was created.  PL/Perl has definitely seen a lot more activity.

I would love to know why PL/Python can't be incrementally improved like
the rest of our code.

-- 
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +