Emanuel Barry added the comment: I see the function is private; is there any concern with extending the PyErr_* API? I think it'd make sense to expose it, since it's a convenient way to do in C what can already be done easily in Python, but I don't actually have a good reason :)
Other than this small nitpick, this LGTM. (Alternatively, we can keep it private for 3.6 and revise that decision for 3.7) ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue28410> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
