➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author brett.cannon
Recipients Tristan Croll, brett.cannon, serhiy.storchaka, vstinner
Date 2017-03-10.18:19:17
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1489169957.95.0.191175929167.issue29758@psf.upfronthosting.co.za>
In-reply-to
Content 
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.
History
Date User Action Args
2017-03-10 18:19:17brett.cannonsetrecipients: + brett.cannon, vstinner, serhiy.storchaka, Tristan Croll
2017-03-10 18:19:17brett.cannonsetmessageid: <1489169957.95.0.191175929167.issue29758@psf.upfronthosting.co.za>
2017-03-10 18:19:17brett.cannonlinkissue29758 messages
2017-03-10 18:19:17brett.cannoncreate