pgsql: configure: Update python search order

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: configure: Update python search order
Date: 2019-09-08 17:45:48
Message-ID: E1i71G0-0000Oy-DF@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

configure: Update python search order

Some systems don't ship with "python" by default anymore, only
"python3" or "python2" or some combination, so include those in the
configure search.

Back-patch of commit 7291733ac. At the time that was only pushed
back as far as v10, because of concerns about interactions with
commit b21c569ce. Closer analysis shows that if we just
s/AC_PATH_PROG/AC_PATH_PROGS/, there is no effect on the older
branches' behavior when PYTHON is explicitly specified, so it should
be okay to back-patch: this will not break any configuration that
worked before. And the need to support platforms with only a
"python3" or "python2" executable is getting ever more urgent.

Original patch by Peter Eisentraut, back-patch analysis by me

Discussion: https://www.postgresql.org/message-id/flat/1457.1543184081%40sss.pgh.pa.us#c9cc1199338fd6a257589c6dcea6cf8d

Branch
------
REL9_5_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/f1a9abe61fef1be9a6085baa2856f2c51d508728

Modified Files
--------------
config/python.m4 | 13 ++++++++++---
configure | 9 +++++++--
doc/src/sgml/installation.sgml | 3 ++-
3 files changed, 19 insertions(+), 6 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Alexander Korotkov 2019-09-08 19:30:34 pgsql: Fix handling of NULL distances in KNN-GiST
Previous Message Peter Eisentraut 2019-09-08 14:34:49 pgsql: Fix behavior of AND CHAIN outside of explicit transaction blocks