Nathan Hartman wrote on Tue, 05 Nov 2019 04:48 +00:00: > Support for Python 3.x: > > Python 3.x and newer are now supported by Subversion's swig-py bindings > and automated test suite. Python 2.7 is still supported. > > Support for Python 2.7 to be 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. All users > are encouraged to move to Python 3. >
Neither maintenance releases nor even security patches. > Subversion 1.14 continues to support Python 2.7 to ease the transition > to Python 3 for those who have not yet made the jump. As Subversion > 1.14 is a Long Term Support (LTS) release, this gives system operators > four additional years of Subversion support for Python 2.7. Note, > however, that Subversion 1.15 and beyond will gradually phase out > support for Python 2.7. I'm not comfortable with committing to supporting Python 2.7 for the lifetime of the 1.14 branch — which basically means until the next LTS, whenever that _actually_ is — when that Python version has been EOL'd upstream. I'd prefer to state that Python 2.7 works (as a point of fact), but support therefor might be dropped at any time, even in a 1.14.x patch release, at our discretion; and we don't promise to fix bugs that affect Python 2.7 only. Of course, we'd not drop support without a good reason, but I'd like us to have the option to do that. After all, if a security vulnerability is found in Python 2 in 2020, it might be impractical for us to even _find_ a Python 2 interpreter to build and test with.
