[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: py2.7 used by default when py2 and py3 are both available

From: Daniel Shahaf <d.s_at_daniel.shahaf.name>
Date: Fri, 15 May 2020 18:42:46 +0000

Branko Čibej wrote on Fri, 15 May 2020 18:14 +00:00:
> On 15.05.2020 19:19, Daniel Shahaf wrote:
> > I just noticed that when I ran «make check» on trunk, it was run using
> > python 2.7. I hadn't pass any Python-related flags to autogen.sh/configure.
> >
> > I presume py2.7 was used because build/find_python.sh used whatever the
> > "python" executable in my $PATH is.
> >
> > Looking at find_python.sh, that's exactly what it does. Shouldn't we
> > change it to use Python 3 in preference to Python 2, given that we've
> > documented py2 as no longer supported?
> Did we actually document that? My impression was that we want to support
> both.

The documentation <https://subversion.apache.org/docs/release-notes/1.14#python2>

    """This means that although Subversion 1.14.0 still technically works
    with Python 2.7, any later 1.14.x point release may drop this
    support if it becomes too difficult to maintain."""

> It would make sense to prefer Python3 over Python2 by default if both
> are available, but I wouldn't go further than that. The order of
> executable names should be [python3, python, python2], IIUC the naming
> conventions.

Sounds good to me.

If we make this change, should we roll an rc3 for it? Otherwise, if we
in fact pull py2.7 support at some point (as the release notes allow us
to), we'd find ourselves having to bump a dependency's major version in
a patch release.


Received on 2020-05-15 20:43:24 CEST

This is an archived mail posted to the Subversion Dev mailing list.