Johan Corveleyn wrote on Wed, 16 Oct 2019 12:12 +00:00: > 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?
+1 > 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 > bindings? Good question. Cheers, Daniel
