Re: Python versions (was Re: RHEL 8.0 build)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Python versions (was Re: RHEL 8.0 build)
Date: 2019-01-16 16:30:28
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> writes:
> On 07/01/2019 00:16, Tom Lane wrote:
>> BTW, this is a pre-existing problem not the fault of this patch,
>> but while we're fooling with the behavior of python lookup would
>> be a great time to fix it: we should add something like
>> AC_ARG_VAR([PYTHON], [path to Python executable])

> Patch attached.

LGTM. I'm slightly annoyed that configure's help output doesn't list
the variables in alphabetical order, but that seems to be a pre-existing
problem that we likely can't fix.

> The following are listed but don't affect any other tests, so I didn't
> include them:


(slightly confused ...) Surely XML2_CONFIG feeds into what we choose for
CPPFLAGS? If that doesn't matter, why not?

regards, tom lane

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Gierth 2019-01-16 16:32:20 Re: draft patch for strtof()
Previous Message Peter Eisentraut 2019-01-16 16:22:29 Re: insensitive collations