Xiang Zhang added the comment: > Easiest fix would be to make do_raise test for both NULL and None, but I'd > really consider fixing the new thread initialization if possible.
I think the easiest fix is OK. The new thread initialization is consistent and should not be changed. The Py_None seems to be set in somewhere in ceval but I am not sure where. You can see at https://hg.python.org/cpython/file/tip/Python/ceval.c#l1200 both NULL and Py_None are checked. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue27558> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
