| From: | James Pye <lists(at)jwp(dot)name> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | pgsql-hackers(at)postgresql(dot)org, Andrew Dunstan <andrew(at)dunslane(dot)net>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, 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 22:43:05 |
| Message-ID: | C7401DA6-C02A-4C3F-A60E-160A871E6F13@jwp.name |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On May 29, 2009, at 1:17 AM, Peter Eisentraut wrote:
> 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.
Yeah, I wasn't meaning to imply tossing 2.x out...
| From | Date | Subject | |
|---|---|---|---|
| Next Message | decibel | 2009-05-29 23:44:46 | Re: Allow vacuumdb to only analyze |
| Previous Message | Robert Haas | 2009-05-29 22:18:08 | Re: search_path vs extensions |