On Fri, Mar 27, 2020 at 11:55:16AM +0900, Yasuhito FUTATSUKI wrote: > On 2020/03/27 8:55, Stefan Sperling wrote: > > Can anyone tell whether we need to pass additional options to > > swig via SWIG_PY_OPTS at this stage? Do we need -py3 for example? > > If we use 3.0.10 <= SWIG < 4.0.0 in release process and want to > generate code for Python 3: > > SWIG_PY_OPTS="-python -py3 -nofastunpack -modern" > > If we use SWIG >= 4.0.0 and want to generate code for Python 3: > > SWIG_PY_OPTS="-python -py3 -nofastunpack" > > If we want to generate code for Python 2, use 1.3.24 <= SWIG < 4.0.0 and > > SWIG_PY_OPTS="-python -classic"
Our release tooling currently uses swig 3.0.12. This version is set in the file tools/dist/release-lines.yml. > We can't bundle code for Python 3 and Python 2 at the same time. Then we should obviously go for Python 3. I have switched to "-python -py3 -nofastunpack -modern" in r1875762. Thank you for your advice :)
