From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Subject: Re: drop support for Python 2.3
Date: Tue, 07 Feb 2017 23:49:03 -0500
Message-ID: <9516.1486529343@sss.pgh.pa.us> (raw)
In-Reply-To: <7d5073f6-d9ea-ab09-4805-69a12f23e52f@2ndquadrant.com>
References: <7d5073f6-d9ea-ab09-4805-69a12f23e52f@2ndquadrant.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>
Peter Eisentraut <peter.eisentraut@2ndquadrant.com> writes:
> I would like to propose that we drop support for Python 2.3.
> ...
> We do have buildfarm coverage on prairiedog. However, that runs a >10
> year old operating system, so I think it is not representing real usage.
I have no particular objection to dropping 2.3 support, but should we
make some effort to fail gracefully (ie, with a relevant error message)
on older versions? I would guess that the effect of your patch will be
to produce quite opaque failures. We seem to be computing python_version
in configure, so it shouldn't be that hard to check.
> - It's unlikely that Python 2.3 is still used in practice. Python 2.4
> is in RHEL 5, which is the typically the oldest mainstream OS we look at.
Hm, is there anything running 2.4 in the buildfarm? If we're going to
claim support for 2.4, we'd be well advised to test it.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: tgl@sss.pgh.pa.us, peter.eisentraut@2ndquadrant.com
Subject: Re: drop support for Python 2.3
In-Reply-To: <9516.1486529343@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox