Serhiy Storchaka added the comment: OK, now I understand. Since _PyErr_BadInternalCall() is private function, we will not break any code. Since it is used only by the PyErr_BadInternalCall() macro and always called with string literal as an argument, C++ user can't use PyErr_BadInternalCall() (without a trick described below). Thus the patch fixes a bug. Thank you Jeroen.
The workaround for unpatched Python 2.7 is to undefine the PyErr_BadInternalCall() macro. #undef PyErr_BadInternalCall There is the PyErr_BadInternalCall() function hidden by the macro. It provides less detailed error message, without file name and line number. ---------- assignee: -> serhiy.storchaka stage: -> commit review type: -> compile error _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue26476> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com