Skip site navigation (1) Skip section navigation (2)

Re: plpython3

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
To: Nathan Boley <npboley(at)gmail(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, James William Pye <lists(at)jwp(dot)name>, Greg Smith <greg(at)2ndquadrant(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Josh Berkus <josh(at)agliodbs(dot)com>, PostgreSQL-development Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: plpython3
Date: 2010-02-01 20:12:41
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
On Mon, 2010-02-01 at 12:01 -0800, Nathan Boley wrote:
> > On the basis of all of the foregoing, I don't think we can consider
> > this patch further for this CommitFest and will update
> > accordingly.
> FWIW, I am very excited about this patch and would be happy to review
> it but have been very busy over the past month. If I can promise a
> review by Thursday morning could we keep it active? Hopefully, at the
> very least, I can provide some useful feedback and spawn some
> community interest.
> I am worried that there is a bit of a chicken and an egg problem with
> this patch. 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. From the documentation, this patch seems like
> an enormous step in the right direction.

I am a +1

Joshua D. Drake

> -Nathan

-- Major Contributor
Command Prompt, Inc: - 503.667.4564
Consulting, Training, Support, Custom Development, Engineering
Respect is earned, not gained through arbitrary and repetitive use or Mr. or Sir.

In response to

pgsql-hackers by date

Next:From: Robert HaasDate: 2010-02-01 20:13:43
Subject: Re: plpython3
Previous:From: Nathan BoleyDate: 2010-02-01 20:01:28
Subject: Re: plpython3

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group