SWIG generates different code when having docstrings

It was observed in ~~#828~~ and ~~#830~~ that SWIG (at least 3.0.8) generates different code depending whether docstrings are available. In particular, with docstrings function signatures are available in generated code while without docstrings swig generates function signatures too but then overwrites function definition by assigning from C++ proxy. That results for instance in Python not knowing about kewyword arguments function is taking.

This is rather a SWIG bug. We can go several ways: report upstrem or check it has been solved, or generate dummy docstrings (when building without doc) as @trlandet suggested, or just solve it case by case where needed (like here bceb7f9cf33552b03bbe7ef34e6575f8821d1699).

Keeping 2017.1 milestone for case we decide for the dummy docstrings solution which might be easy for @trlandet.

Comments (2)