| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: Back-patch support for python 2.5? |
| Date: | 2007-10-14 17:18:57 |
| Message-ID: | 200710141918.58900.peter_e@gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> I noticed that two of the buildfarm members are failing the 8.1
> branch because they're trying to build plpython with python 2.5. To
> get that to work, I think we'd need to back-patch these two fixes:
> http://archives.postgresql.org/pgsql-committers/2006-11/msg00165.php
> http://archives.postgresql.org/pgsql-committers/2007-04/msg00043.php
> Is that worth doing? Should we go further back than 8.1?
I find these patches a bit excessive for backporting, especially 10
minor releases into the branch.
Those who need Python 2.5 can use PostgreSQL 8.2. I consider that to be
a new feature. The fact that the buildfarm exercises other
combinations isn't evidence of a practical need.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-10-14 19:10:39 | Re: Back-patch support for python 2.5? |
| Previous Message | Gokulakannan Somasundaram | 2007-10-14 16:30:20 | Re: Including Snapshot Info with Indexes |