Branko Čibej wrote:
What Py3 support are we talking about anyway? svn build? svn test
suite? swig-py bindings?
This is about the work that's happening on the swig-py3 branch. So: that
would be support for building the swig-py bindings for both Python3 and
Python2. Trunk only support Python2 which has reached end of life.
Our build and test scripts have already been modified to work with both
variants of Python, or rather, with Python 2.7.x and 3.something, for
some unknown value of "something."
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 support is needed if we want to backport Py3 support to 1.10.x,
which would be a good thing to aim for; and given that dual-Py-version
capability is mostly in place but unfinished, that sounds like we are on
the right track to be confident that if we put it on trunk now we would
be able to fix up the Py2 support for backport to 1.10.x later, when
it's ready.
It may be tempting to "just" try to fix the remaining Py2 issues right
now before merge to trunk, but I need to prepare a 1.13 branch within
the next 10 days to stay on schedule, so please consider prioritising
merge to trunk with Py3 working, leaving Py2 to be fixed up after that.
- Julian
