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

From Andrew Dunstan
Subject Re: Python 3.0 does not work with PL/Python
Date
Msg-id 4A1F3506.9030703@dunslane.net
Whole thread Raw
In response to Re: Python 3.0 does not work with PL/Python  (Alvaro Herrera <alvherre@commandprompt.com>)
Responses Re: Python 3.0 does not work with PL/Python  (Caleb Welton <cwelton@greenplum.com>)
Re: Python 3.0 does not work with PL/Python  (Peter Eisentraut <peter_e@gmx.net>)
Re: Python 3.0 does not work with PL/Python  (Sam Mason <sam@samason.me.uk>)
Re: Python 3.0 does not work with PL/Python  (David Blewett <david@dawninglight.net>)
List pgsql-hackers

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.
>   

Does Python 3 have some sort of usable sandbox that would mean we could 
have a trusted plpython?

Otherwise, I'm not too keen simply to throw Python 2.x overboard until 
it's no longer common on platforms people are likely to want to install 
Postgres on, if that's what's implied by the original question.

cheers

andrew


pgsql-hackers by date:

Previous
From: Josh Berkus
Date:
Subject: Re: pg_migrator and an 8.3-compatible tsvector data type
Next
From: Robert Haas
Date:
Subject: Re: User-facing aspects of serializable transactions