| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Time to drop plpython2? |
| Date: | 2021-11-15 18:18:22 |
| Message-ID: | 2142324.1637000302@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andres Freund <andres(at)anarazel(dot)de> writes:
> On 2021-11-15 12:19:51 -0500, Tom Lane wrote:
>> I was wondering about simply probing to see if python3 exists (and if
>> so, what version it is exactly), as an additional configure test that
>> doesn't hook into anything. That would give us some information without
>> suddenly changing what is being tested.
> But this is probably a good compromise. Were you thinking of doing a proper
> autoconf test or just putting something like python3 --version || true in
> configure?
Hm, I had in mind an actual configure test; but since it's just a
temporary exploratory measure, shortcuts are fine. However, I'm
not sure that what you suggest would result in capturing anything
in config.log.
> I guess it'd be easiest to interpret if we output the current PYTHON version
> and, iff < 3.0, also output the 'python3' version?
We'll already know if PYTHON is set, at least so far as the buildfarm
is concerned.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2021-11-15 18:34:15 | Re: [RFC] building postgres with meson |
| Previous Message | Andres Freund | 2021-11-15 18:12:46 | Re: Time to drop plpython2? |