Issue #18408: PyObject_Str(), PyObject_Repr() and type_call() now fail with an

assertion error if they are called with an exception set (PyErr_Occurred()).

As PyEval_EvalFrameEx(), they may clear the current exception and so the caller
looses its exception.
This commit is contained in:
Victor Stinner 2013-07-18 01:49:30 +02:00
parent 4abda5d5b0
commit 8e47832737
2 changed files with 23 additions and 0 deletions

View file

@ -736,6 +736,13 @@ type_call(PyTypeObject *type, PyObject *args, PyObject *kwds)
return NULL;
}
#ifdef Py_DEBUG
/* type_call() must not be called with an exception set,
because it may clear it (directly or indirectly) and so the
caller looses its exception */
assert(!PyErr_Occurred());
#endif
obj = type->tp_new(type, args, kwds);
if (obj != NULL) {
/* Ugly exception: when the call was type(something),