Georg Brandl ge...@python.org added the comment:
Documented PyErr_PrintEx() in r69292.
--
resolution: - fixed
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue5096
___
New submission from Kandalintsev Alexandre bug_hun...@messir.net:
When unhandled in python code exception occurs in PyObject_CallMethod
frame_dealloc() (Objects/frameobject.c:422)
not called. Even if I call PyErr_Print().
But if I call PyErr_Clear() then all okay. Documentation says that
Amaury Forgeot d'Arc amaur...@gmail.com added the comment:
I think I have an explanation:
When a python exception is raised, the current call stack is stored in
the exception state (tstate-curexc_traceback). This includes all the
living frame objects, with all their local variables.
This
Kandalintsev Alexandre bug_hun...@messir.net added the comment:
Thank you for your activity. This feature drank alot of my blood. Please
document this or change behavior.
PS Older python versions may be also affected so changing behavior may
brake existing code :(
Changes by Amaury Forgeot d'Arc amaur...@gmail.com:
--
assignee: - georg.brandl
components: +Documentation -Interpreter Core
nosy: +georg.brandl
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue5096
