| From: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Python installation selection in Meson |
| Date: | 2023-11-30 06:30:22 |
| Message-ID: | 69a5d315-d1c1-4dc4-b3c5-868e5f5c8a8c@eisentraut.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 28.11.23 19:16, Andres Freund wrote:
> On 2023-11-28 19:02:42 +0100, Peter Eisentraut wrote:
>> I noticed that under meson, the selection of the Python installation using
>> the 'PYTHON' option doesn't work completely. The 'PYTHON' option determined
>> the Python binary that will be used to call the various build support
>> programs. But it doesn't affect the Python installation used for PL/Python.
>> For that, we need to pass the program determined by the 'PYTHON' option back
>> into the find_installation() routine of the python module. (Otherwise,
>> find_installation() will just search for an installation on its own.) See
>> attached patch. I ran this through Cirrus, seems to work.
>
> Makes sense!
I have committed this, and also backpatched to 16 to keep the behavior
consistent.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2023-11-30 07:03:44 | Re: GUC names in messages |
| Previous Message | Kyotaro Horiguchi | 2023-11-30 06:29:49 | Re: GUC names in messages |