Message261169
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. |
|
Date |
User |
Action |
Args |
2016-03-03 16:11:42 | serhiy.storchaka | set | recipients:
+ serhiy.storchaka, nnorwitz, jdemeyer |
2016-03-03 16:11:42 | serhiy.storchaka | set | messageid: <1457021502.91.0.553127142575.issue26476@psf.upfronthosting.co.za> |
2016-03-03 16:11:42 | serhiy.storchaka | link | issue26476 messages |
2016-03-03 16:11:42 | serhiy.storchaka | create | |
|