STINNER Victor added the comment: pyerr_match_clear-2.patch: Updated patch, more complete (I also removed the assertions, I only added to debug).
> Since my patch makes assumption on which exception is expected, it can change > the behaviour of functions if I forgot a different exception which is also > supposed to be replaced. To reduce risks, we can just remove the new PyErr_ExceptionMatches() checks from the patch in a first time, and add them later, while being very careful. Calling PyErr_Clear() where exceptions must not be chained should be enough for a first step. ---------- Added file: http://bugs.python.org/file38677/pyerr_match_clear-2.patch _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue23763> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
