Re: Python 3.0 does not work with PL/Python - Mailing list pgsql-hackers

From James Pye
Subject Re: Python 3.0 does not work with PL/Python
Date
Msg-id 047AB82B-1AC8-4177-9CAC-88D506908A4E@jwp.name
Whole thread Raw
In response to Re: Python 3.0 does not work with PL/Python  (Peter Eisentraut <peter_e@gmx.net>)
List 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.


pgsql-hackers by date:

Previous
From: Zdenek Kotala
Date:
Subject: Re: libpq is not thread safe
Next
From: Magnus Hagander
Date:
Subject: Re: "could not reattach to shared memory" captured in buildfarm