| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, James Pye <lists(at)jwp(dot)name>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Marko Kreen <markokr(at)gmail(dot)com> |
| Subject: | Re: Python 3.0 does not work with PL/Python |
| Date: | 2009-05-29 08:12:05 |
| Message-ID: | 200905291112.06032.peter_e@gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Friday 29 May 2009 03:53:17 Alvaro Herrera wrote:
> Bruce Momjian escribió:
> > Peter Eisentraut wrote:
> > > On Monday 06 April 2009 02:10:59 James Pye wrote:
> > > > Any thoughts on the acceptability of a complete rewrite for Python 3?
> > >
> > > http://www.joelonsoftware.com/articles/fog0000000069.html
> >
> > You usually have to rewrite when you have not done refactoring as part
> > of development; PGDG does refactoring regularly.
>
> Except that plpython stagnates, save for minor hacks here and there.
But that doesn't mean that there is anything wrong with it. Of course there
is, but those are isolated problems that can be fixed when desired. For
example, it might just be that those who use it don't have use of INOUT
parameters or table returns.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2009-05-29 08:17:02 | Re: Python 3.0 does not work with PL/Python |
| Previous Message | Peter Eisentraut | 2009-05-29 08:06:28 | Re: bytea vs. pg_dump |