On 11/01/2015 07:08 AM, James McCoy wrote: > On Sat, Oct 24, 2015 at 11:48:24PM +0200, Matthias Klose wrote: >> As seen in #802906, this now becomes an RC issue, as Python 3.5 is a >> supported Python version, and is not anymore supported by swig 2.0. >> >> Same for octave 4.0, and maybe other languages. > Not everything that worked with swig2.0 works with swig3.0 (e.g., > subversion's swig bindings). Why can't both be shipped? I think they could be shipped but shouldn't.
For one swig 2.0 it not maintained upstream anymore. The other thing is that swig 3.0 should be usable to build subversion, so I have to get this fixed instead of using swig 2.0 as the way out. Greetings, Torsten
