Serhiy Storchaka added the comment: How this can help reduce the possible errors? I afraid that it rather can increase the possibility of error.
There is no undefined behaviour in current code. It was in old code (in the casting a pointer to PyObject*), but this was fixed with new PyObject_HEAD in 3.0+. 2.7 still has this undefined behaviour. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue26824> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
