[issue29758] Previously-working SWIG code fails in Python 3.6
Brett Cannon
report at bugs.python.org
Fri Mar 10 13:19:17 EST 2017
Brett Cannon added the comment:
Please keep this issue closed until you hear back from the SWIG team. Just because your code worked under Python 3.5 doesn't mean SWIG didn't accidentally emit something that breaks under Python 3.6 because we started being more stringent about something. Basically unless we have C code (and not SWIG or C++ code) to reproduce this then we have to go on the assumption it's a problem on SWIG's side.
----------
resolution: -> third party
status: open -> closed
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29758>
_______________________________________
More information about the Python-bugs-list
mailing list