From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: Heikki Linnakangas <hlinnaka@iki.fi>
Cc: pgsql-docs <pgsql-docs@postgresql.org>
Subject: Re: Obsolete warning on Python 2.4
Date: Tue, 20 Sep 2016 16:27:22 -0400
Message-ID: <20976.1474403242@sss.pgh.pa.us> (raw)
In-Reply-To: <04f81c77-ee67-5604-4297-ecd8969d3cf3@2ndquadrant.com>
References: <85e377b2-d459-396e-59b1-115548bbc059@iki.fi>
<04f81c77-ee67-5604-4297-ecd8969d3cf3@2ndquadrant.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-docs>
Peter Eisentraut <peter.eisentraut@2ndquadrant.com> writes:
> On 9/19/16 1:21 AM, Heikki Linnakangas wrote:
>> That seems uninteresting to anyone in 2016. Any objections to removing it?
> We're still maintaining compatibility with Python 2.4 and the bug
> apparently still exists, so I would perhaps keep it until we kill
> support for Python 2.4.
Since the bug doesn't happen in production builds of Python, only in
debug builds, I'm not really worried that it's still a factor, even
if you believe that the Python folk still haven't patched it.
In short, I agree with Heikki that we could remove this.
regards, tom lane
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
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-docs@postgresql.org
Cc: tgl@sss.pgh.pa.us, peter.eisentraut@2ndquadrant.com, hlinnaka@iki.fi
Subject: Re: Obsolete warning on Python 2.4
In-Reply-To: <20976.1474403242@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