mirror of
https://github.com/postgres/postgres.git
synced 2025-07-30 11:03:19 +03:00
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 commit7291733ac
. At the time that was only pushed back as far as v10, because of concerns about interactions with commitb21c569ce
. 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
This commit is contained in:
@ -1441,7 +1441,8 @@ su - postgres
|
||||
<![%standalone-include[the <application>PL/Python</>
|
||||
documentation]]>
|
||||
<![%standalone-ignore[<xref linkend="plpython-python23">]]>
|
||||
for more information.
|
||||
for more information. If this is not set, the following are probed
|
||||
in this order: <literal>python python3 python2</literal>.
|
||||
</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
Reference in New Issue
Block a user