From: Gregory P. Smith Date: Wed, 27 Feb 2019 23:27:32 +0000 (-0800) Subject: Document the surprising sideeffect PyErr_Print(). (#12081) X-Git-Tag: v3.8.0a3~218 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=4173772031747a9b249be4100b4aa9eda805ea23;p=thirdparty%2FPython%2Fcpython.git Document the surprising sideeffect PyErr_Print(). (#12081) Did you know an API documented as printing the pending traceback would sometimes exit the process? You do now. --- diff --git a/Doc/c-api/exceptions.rst b/Doc/c-api/exceptions.rst index 6dd0c02c6d7b..8c5f66cbef72 100644 --- a/Doc/c-api/exceptions.rst +++ b/Doc/c-api/exceptions.rst @@ -53,8 +53,12 @@ Printing and clearing .. c:function:: void PyErr_PrintEx(int set_sys_last_vars) Print a standard traceback to ``sys.stderr`` and clear the error indicator. - Call this function only when the error indicator is set. (Otherwise it will - cause a fatal error!) + **Unless** the error is a ``SystemExit``. In that case the no traceback + is printed and Python process will exit with the error code specified by + the ``SystemExit`` instance. + + Call this function **only** when the error indicator is set. Otherwise it + will cause a fatal error! If *set_sys_last_vars* is nonzero, the variables :data:`sys.last_type`, :data:`sys.last_value` and :data:`sys.last_traceback` will be set to the