Re: Python 3.0 does not work with PL/Python

From: James Pye <lists(at)jwp(dot)name>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: pgsql-hackers(at)postgresql(dot)org, 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-04 08:18:50
Message-ID: 047AB82B-1AC8-4177-9CAC-88D506908A4E@jwp.name
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On May 3, 2009, at 11:02 PM, Peter Eisentraut wrote:
>
> http://www.joelonsoftware.com/articles/fog0000000069.html

Good read. =)

However, complete rewrite being relative in this case:

WIP: http://github.com/jwp/postgresql-plpython3/tree/c804e693b6a0df98c0e5c465e75ba2e9014ebf37/src/pl/plpython3

That is, from pgsql's perspective it would be a complete rewrite.

From my perspective it would be a refactored version of plpy for
Python 3.x and pgsql 8.5/head. Additionally, plpy originally came from
plpythonu(7.3 or 7.4), but was *massively* refactored(read:
effectively rewritten).

I wouldn't want to start from scratch, actually.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Magnus Hagander 2009-05-04 08:29:12 Re: "could not reattach to shared memory" captured in buildfarm
Previous Message Magnus Hagander 2009-05-04 08:13:18 Re: windows shared memory error