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

Re: [offlist] Re: Merging branches/swig-py3 to trunk

From: Julian Foad <julianfoad_at_apache.org>
Date: Fri, 8 Nov 2019 08:13:20 +0000

Nathan Hartman wrote:
> Question: Some Python scripts have not been updated for Python 3.x
> yet. Should those be listed in the release notes under "Known Issues"?
> Should a bug be filed? Or both?

Both: an Issue tracking which ones are known broken or untested, and a
pointer to it in the release notes.

> The updated text:
>
> [[[
>
> Support for Python 3.x:
>
> Some optional features of Subversion utilize the Python scripting
> language.
>
> Subversion's SWIG Python bindings and automated test suite now support
> Python 3.x (and newer).
>
> Support for Python 2.7 is being phased out:
>
> As of 1 January 2020, Python 2.7 has reached end of life. This means
> that Python 2.7 will no longer receive maintenance releases or
> patches, even for security issues. All users are strongly encouraged
> to move to Python 3.
>
> As Subversion 1.14 is a Long Term Support (LTS) release with planned
> support into 2024, well beyond end-of-life for Python 2.7, the
> Subversion developers cannot commit to supporting and testing with
> Python 2.7, or to fixing bugs that affect Python 2.7 only, for the
> duration of this support period.
>
> 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.
>
> If you must continue using Python 2.7, our previous Long Term Support
> release, Subversion 1.10, is supported until 2022. Python 2.7 support
> will not be removed from Subversion 1.10.
>
> Note that Subversion does not require Python for its basic operation.
> If you are not using Subversion's SWIG Python bindings, automated test
> suite, or other Python-coded tools that ship with Subversion, this
> change does not affect you.
>
> ]]]

Sounds good to me.

Maybe add a note that in "3.x" we intend to choose a specific "x", in
case we forget to update the text when we choose one?

I think it would be useful to have the info also available in summary
form, a small table. We might want to put the summary in various
places, not just in the release notes but in maybe another web page
and/or emails etc. Something like:

svn 1.9 Py 2.7 supported, Py 3.x not working
svn 1.10 Py 2.7 supported, Py 3.x+ supported for build & test, not
working for bindings (?)
svn 1.14 Py 2.7 unsupported (working in 1.14.0), Py 3.x supported

For 1.10 I am offering an example of the form of summary, not sure what
the actual status is.

If I did my search correctly, there is nothing about Python 3 in any of
the 1.10 through 1.14 release notes. Haven't we got something to say
about limited support (for build and test?) in some version before 1.14?
  All I could find was one py3 build fix (r1819444) merged to 1.10.x.

- Julian
Received on 2019-11-08 09:13:24 CET

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