On 2019/10/21 19:55, Jun Omae wrote:
Hi,
I'm trying to build and test swig-py3 branch (r1868677) on Ubuntu 16.04 with
Python 3.7, however I get FAILED(failures=16, errors=22) from the unit tests.
Investigating the issue with helps of Yasuhito, that is caused by using old
SWIG version with no SWIG_PYTHON_STRICT_BYTE_CHAR feature. The
SWIG_PYTHON_STRICT_BYTE_CHAR feature is available since SWIG 3.0.9 but SWIG is
3.0.8 in Ubuntu 16.04.
I consider that we should warn the required SWIG version at least.
[1] https://github.com/swig/swig/blob/rel-3.0.10/CHANGES#L160
Thank you for your report. I think if that feature or some other changes on
swig-py3 breaks Python 2 (or accidentally Ruby and/or Perl bindings),
we should bump required SWIG verersion or resolve issues with older SWIGs.
However if it affect only with Python 3, we only need to restrict
per Language bindings requirement.
Anyway, I think we need more test with older SWIG (or restrict required
SWIG version if we can't test).
Thanks,
--
Yasuhito FUTATSUKI <futat...@poem.co.jp>
