On Wed, Oct 16, 2019 at 1:37 PM Yasuhito FUTATSUKI <[EMAIL PROTECTED]> wrote:
This makes me wonder: should that be fixed specifically on trunk, and
nominated for backport to 1.13, so we can possibly claim basic support
for Python 3 in our build and test processes (in at least one released
version) before the end of this year?
Or should we reintegrate the swig-py3 branch ASAP, and nominate *that*
for backport to 1.13, so we can have Python 3 support, including swig