Re: Time to drop plpython2?

Поиск
Список
Период
Сортировка
Искать
От
Tom Lane
Тема
Re: Time to drop plpython2?
Дата
Msg-id
2142324.1637000302@sss.pgh.pa.us
Список
Дерево обсуждения
Time to drop plpython2? Andres Freund <andres@anarazel.de>
Re: Time to drop plpython2? Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Re: Time to drop plpython2? Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Re: Time to drop plpython2? Andres Freund <andres@anarazel.de>
Re: Time to drop plpython2? Tom Lane <tgl@sss.pgh.pa.us>
Re: Time to drop plpython2? Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Re: Time to drop plpython2? Tom Lane <tgl@sss.pgh.pa.us>
Re: Time to drop plpython2? Andrew Dunstan <andrew@dunslane.net>
Re: Time to drop plpython2? Andrew Dunstan <andrew@dunslane.net>
Re: Time to drop plpython2? Tom Lane <tgl@sss.pgh.pa.us>
Re: Time to drop plpython2? Andres Freund <andres@anarazel.de>
Re: Time to drop plpython2? Thomas Munro <thomas.munro@gmail.com>
Andres Freund  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


В списке pgsql-hackers по дате отправления
От: Tom Lane
Дата:
От: Andres Freund
Дата:
FAQ