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
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
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 mat
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 Python
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 from
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 m
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
AC_ARG_VAR([PY
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 ca
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 Eisent
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 i
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 l
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 commands
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*
> > /usr/loc
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 bi
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 it'
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 inheren
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 yet.
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
Hi,
On 2018-11-24 15:49:25 -0500, Tom Lane wrote:
> Jeremy Harris writes:
> > Trying to set up a buildfarm animal on a RHEL 8.0 (beta) system,
> > the build fails early:
> > ...
> > It appears to be a "configure" script looking for python; and there is
> > no such. You can have python3 or pytho
On 11/24/18 3:49 PM, Tom Lane wrote:
Jeremy Harris writes:
Trying to set up a buildfarm animal on a RHEL 8.0 (beta) system,
the build fails early:
...
It appears to be a "configure" script looking for python; and there is
no such. You can have python3 or python2 - but neither package insta
Jeremy Harris writes:
> Trying to set up a buildfarm animal on a RHEL 8.0 (beta) system,
> the build fails early:
> ...
> It appears to be a "configure" script looking for python; and there is
> no such. You can have python3 or python2 - but neither package install
> provides a symlink of just "
21 matches
Mail list logo
