Guido Goldstein wrote:
> Is it possible to tell me which python versions you want to
> support?

The issue isn't so much which versions we want to support.  There is 
certainly some flexibility with that.  But when a patch breaks the 
buildfarm a) unannounced and b) without any apparent feature gain, then 
people get annoyed.

That said, we certainly try to support a few more versions of Python 
than just the last one, but I'm not sure anyone knows which ones 
exactly.  As a data point: Quite probably, Python 2.5 does *not* work 
with anything <= 8.1, so it would be nice if we could give the Python 
2.4 users the option of not having to upgrade to Python 2.5 at the same 
time as upgrading to PostgreSQL 8.2.  This doesn't really govern your 
8.3 patch, however.

-- 
Peter Eisentraut
http://developer.postgresql.org/~petere/

In response to

• Re: pgsql: Fix for plpython functions; return true/false for boolean, at 2007-01-30 10:43:52 from Guido Goldstein

Responses

• Re: [HACKERS] pgsql: Fix for plpython functions; return true/false for boolean, at 2007-01-30 13:52:56 from Guido Goldstein

pgsql-hackers by date

Next:	From: Guido Goldstein	Date: 2007-01-30 13:52:56
	Subject: Re: [HACKERS] pgsql: Fix for plpython functions; return true/false for boolean,
Previous:	From: Andrew Dunstan	Date: 2007-01-30 12:19:33
	Subject: Re: Phantom Command IDs, updated patch

pgsql-committers by date

Next:	From: Guido Goldstein	Date: 2007-01-30 13:52:56
	Subject: Re: [HACKERS] pgsql: Fix for plpython functions; return true/false for boolean,
Previous:	From: Guido Goldstein	Date: 2007-01-30 10:43:52
	Subject: Re: pgsql: Fix for plpython functions; return true/false for boolean,

pgsql-patches by date

Next:	From: Guido Goldstein	Date: 2007-01-30 13:52:56
	Subject: Re: [HACKERS] pgsql: Fix for plpython functions; return true/false for boolean,
Previous:	From: Andrew Dunstan	Date: 2007-01-30 12:19:33
	Subject: Re: Phantom Command IDs, updated patch