Re: Python versions (was Re: RHEL 8.0 build)

2019-09-08 Thread Tom Lane
Peter Eisentraut writes: > On 2019-09-07 22:18, Tom Lane wrote: >> So this subject has just intruded itself again, because new buildfarm >> member "morepork" is failing in the pre-v10 branches, because ... you >> guessed it ... it has "python3" but not "python". This situation is >> going to get

Re: Python versions (was Re: RHEL 8.0 build)

2019-09-08 Thread Peter Eisentraut
On 2019-09-07 22:18, Tom Lane wrote: > So this subject has just intruded itself again, because new buildfarm > member "morepork" is failing in the pre-v10 branches, because ... you > guessed it ... it has "python3" but not "python". This situation is > going to get worse, not better, as time goes

Re: Python versions (was Re: RHEL 8.0 build)

2019-09-07 Thread Tom Lane 
Peter Eisentraut  writes:
>>> [ patch to search for python, then python3, then python2 ]

> Committed with some documentation updates.

> I only backpatched to PG10, because before that the handling of absolute
> paths vs nonabsolute paths is a bit murky and

Re: Python versions (was Re: RHEL 8.0 build)

2019-01-17 Thread Peter Eisentraut
On 16/01/2019 17:30, Tom Lane wrote: >> The following are listed but don't affect any other tests, so I didn't >> include them: > >> BISON >> DTRACE >> DTRACEFLAGS >> FLEX >> XML2_CONFIG > > (slightly confused ...) Surely XML2_CONFIG feeds into what we choose for > CPPFLAGS? If that doesn't

Re: Python versions (was Re: RHEL 8.0 build)

2019-01-16 Thread Tom Lane
Peter Eisentraut writes: > On 07/01/2019 00:16, Tom Lane wrote: >> BTW, this is a pre-existing problem not the fault of this patch, >> but while we're fooling with the behavior of python lookup would >> be a great time to fix it: we should add something like >> AC_ARG_VAR([PYTHON], [path to

Re: Python versions (was Re: RHEL 8.0 build)

2019-01-16 Thread Peter Eisentraut
On 07/01/2019 00:16, Tom Lane wrote: > BTW, this is a pre-existing problem not the fault of this patch, > but while we're fooling with the behavior of python lookup would > be a great time to fix it: we should add something like > > AC_ARG_VAR([PYTHON], [path to Python executable]) > > Aside

Re: Python versions (was Re: RHEL 8.0 build)

2019-01-13 Thread Peter Eisentraut
On 03/01/2019 18:52, Tom Lane wrote: > Peter Eisentraut writes: >> On 29/11/2018 16:34, Tom Lane wrote: >>> After sleeping on it for awhile, I am liking the idea of probing >>> python, python3, python2 (while keeping the $PYTHON override of >>> course). > >> I think this was the option with the

Re: Python versions (was Re: RHEL 8.0 build)

2019-01-06 Thread Tom Lane
Peter Eisentraut writes: > I think this was the option with the most support. Here is a patch. BTW, this is a pre-existing problem not the fault of this patch, but while we're fooling with the behavior of python lookup would be a great time to fix it: we should add something like

Re: Python versions (was Re: RHEL 8.0 build)

2019-01-03 Thread Tom Lane
Peter Eisentraut writes: > On 29/11/2018 16:34, Tom Lane wrote: >> After sleeping on it for awhile, I am liking the idea of probing >> python, python3, python2 (while keeping the $PYTHON override of >> course). > I think this was the option with the most support. Here is a patch. > I agree we

Re: Python versions (was Re: RHEL 8.0 build)

2019-01-03 Thread Peter Eisentraut
On 29/11/2018 16:34, Tom Lane wrote: > After sleeping on it for awhile, I am liking the idea of probing > python, python3, python2 (while keeping the $PYTHON override of > course). I think this was the option with the most support. Here is a patch. I agree we can backport this. -- Peter

Re: Python versions (was Re: RHEL 8.0 build)

2018-11-29 Thread Tom Lane
Peter Eisentraut writes: > On 28/11/2018 22:41, Tom Lane wrote: >> Peter Eisentraut writes: >>> My suggestion is to either >>> - Change the probe order to python, python3 in master, or >>> - Don't change anything until PEP 394 is updated. >> It's hard to evaluate the latter unless we have some

Re: Python versions (was Re: RHEL 8.0 build)

2018-11-29 Thread Peter Eisentraut
On 28/11/2018 22:41, Tom Lane wrote: > Peter Eisentraut writes: >> My suggestion is to either >> - Change the probe order to python, python3 in master, or >> - Don't change anything until PEP 394 is updated. > > It's hard to evaluate the latter unless we have some idea how soon > that update is

Re: Python versions (was Re: RHEL 8.0 build)

2018-11-28 Thread Tom Lane
Thomas Munro writes: >> On 25/11/2018 23:14, Tom Lane wrote: >>> Also, I noticed on a fresh FreeBSD 12.0 installation that what >>> I've got is [ python2.7 and python3.6 ] > Confirmed that if you pkg install python2 and python3 meta-packages on > a FreeBSD box you get python2 and python3

Re: Python versions (was Re: RHEL 8.0 build)

2018-11-28 Thread Thomas Munro
On Wed, Nov 28, 2018 at 2:14 AM Peter Eisentraut wrote: > On 25/11/2018 23:14, Tom Lane wrote: > > Also, I noticed on a fresh FreeBSD 12.0 installation that what > > I've got is > > > > $ ls /usr/bin/pyth* > > ls: /usr/bin/pyth*: No such file or directory > > $ ls /usr/local/bin/pyth* > >

Re: Python versions (was Re: RHEL 8.0 build)

2018-11-28 Thread Tom Lane
Peter Eisentraut writes: > My suggestion is to either > - Change the probe order to python, python3 in master, or > - Don't change anything until PEP 394 is updated. It's hard to evaluate the latter unless we have some idea how soon that update is likely to happen ... have you heard any little

Re: Python versions (was Re: RHEL 8.0 build)

2018-11-28 Thread Peter Eisentraut
On 27/11/2018 18:30, Andres Freund wrote: > ISTM we should first go for python, python2, python3 in all branches, > and then have a separate master only commit that changes over the order > to prefer python3 over 2. I don't think preferring 3 over 2 would be > appropriate for past branches, but

Re: Python versions (was Re: RHEL 8.0 build)

2018-11-27 Thread Andres Freund
Hi, On 2018-11-27 14:14:24 +0100, Peter Eisentraut wrote: > On 25/11/2018 23:14, Tom Lane wrote: > > Andres Freund writes: > >> On 2018-11-24 15:49:25 -0500, Tom Lane wrote: > >>> There's been some preliminary discussion about starting to default to > >>> python3, but given this project's

Re: Python versions (was Re: RHEL 8.0 build)

2018-11-27 Thread Peter Eisentraut
On 25/11/2018 23:14, Tom Lane wrote: > Andres Freund writes: >> On 2018-11-24 15:49:25 -0500, Tom Lane wrote: >>> There's been some preliminary discussion about starting to default to >>> python3, but given this project's inherent conservatism, I don't expect >>> that to happen for some years

Python versions (was Re: RHEL 8.0 build)

2018-11-25 Thread Tom Lane
Andres Freund writes: > On 2018-11-24 15:49:25 -0500, Tom Lane wrote: >> There's been some preliminary discussion about starting to default to >> python3, but given this project's inherent conservatism, I don't expect >> that to happen for some years yet. In any case, whenever we do pull >> that