On Mon, Sep 2, 2019 at 8:23 AM Julian Foad <julianf...@apache.org> wrote:
> Thanks. I see no reason to make a special effort to have swig-py > bindings still support Python 2 for Subversion 1.13 and 1.14-LTS. In > fact, it's probably best if we explicitly remove Py2 support for 1.14, > to avoid getting trapped in maintenance difficulties. Py2 is EOL 1/1/2020. Keeping it in 1.14 which implies support until 2024 would be a mistake because support will only get harder. Imagine what happens when your OS vendor removes Py2 packages. Even if Py2 still technically "works" with 1.14 (because that makes it easier to support Py3 for the remainder of 1.10), I suggest to document that Py2 is explicitly NOT supported in the 1.14 release notes. The internal policy should be that once 1.10 support ends, changes are allowed to break Py2 support and/or not be tested with Py2. I have (among other things) a Windows 10 machine available to me with Python 2 and 3. I'll be glad to help, with a little guidance. At the very least I can help with testing.
