pgsql: configure: Update python search order - Mailing list pgsql-committers

From Tom Lane
Subject pgsql: configure: Update python search order
Date
Msg-id E1i71G0-0000Oz-DB@gemulon.postgresql.org
Whole thread Raw
List 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_4_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/96db9d5e2b49a4c73108d448adc8f1a485530f5c

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


pgsql-committers by date:

Previous
From: Peter Eisentraut
Date:
Subject: pgsql: Fix behavior of AND CHAIN outside of explicit transactionblocks
Next
From: Alexander Korotkov
Date:
Subject: pgsql: Fix handling of NULL distances in KNN-GiST