On 20.10.2019 04:05, Daniel Shahaf wrote: > Nathan Hartman wrote on Sun, 20 Oct 2019 01:49 +00:00: >> I support this idea even if the soak must restart or be extended. > Brainstorming: How about letting the soak continue but documenting in > the release notes, release announcements, etc., that we'll be adding swig- > py3 support in a patch release? This way, swig-py2 users will know not > to upgrade from 1.12.x until after the destabilizing changes are made.
The thing is that the swig-py3 branch introduces a new dependency (py3c) for Py2 bindings, not just for Py3. That's a big deal even for packagers, IMO. (Which reminds me: get-deps.sh still needs to be updated to download py3c.) > I assume the parts of the swig-py3 branch outside subversion/bindings/ > aren't destabilizing and would not be a concern to backport in a patch > release. Those are mainly test fixes, so sure. -- Brane
