| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, 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:17:02 |
| Message-ID: | 200905291117.03245.peter_e@gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2009-05-29 10:08:15 | Re: search_path vs extensions |
| Previous Message | Peter Eisentraut | 2009-05-29 08:12:05 | Re: Python 3.0 does not work with PL/Python |