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

From Peter Eisentraut
Subject Re: Python 3.0 does not work with PL/Python
Date
Msg-id 200905291117.03245.peter_e@gmx.net
Whole thread Raw
In response to Re: Python 3.0 does not work with PL/Python  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: Python 3.0 does not work with PL/Python  (James Pye <lists@jwp.name>)
List pgsql-hackers
On Friday 29 May 2009 04:06:14 Andrew Dunstan wrote:
> 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.

My guess is that we will need to keep around a Python 2.x version for at least 
another three years, meaning two or three major PostgreSQL releases.

That also means that maintaining a separate, parallel code base for a Python 3 
variant can only be acceptable if it gives major advantages.


pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: Python 3.0 does not work with PL/Python
Next
From: Peter Eisentraut
Date:
Subject: Re: search_path vs extensions