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 abarry
Recipients Rosuav, abarry, ethan.furman, georg.brandl, ncoghlan, xiang.zhang
Date 2016-07-23.15:16:35
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
After discussing with someone, I realized that the tests actually test the Python implementation twice, and never the C implementation (since I use traceback.print_exc() to "test" the C implementation).

I don't think it's possible to both catch the output from the C implementation and prevent it from exiting out of the function prematurely, but if anyone knows how to do that, be my guest! In the meantime, I'm going to mess about with _testcapi and see if I can add something there to help with this.
Date User Action Args
2016-07-23 15:16:36abarrysetrecipients: + abarry, georg.brandl, ncoghlan, ethan.furman, Rosuav, xiang.zhang
2016-07-23 15:16:36abarrysetmessageid: <>
2016-07-23 15:16:36abarrylinkissue26823 messages
2016-07-23 15:16:35abarrycreate