[issue5096] strange thing after call PyObject_CallMethod

Georg Brandl added the comment: Documented PyErr_PrintEx() in r69292. -- resolution: -> fixed status: open -> closed ___ Python tracker ___ _

[issue5096] strange thing after call PyObject_CallMethod

Changes by Amaury Forgeot d'Arc : -- assignee: -> georg.brandl components: +Documentation -Interpreter Core nosy: +georg.brandl ___ Python tracker ___ ___

[issue5096] strange thing after call PyObject_CallMethod

Kandalintsev Alexandre 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 :( ___ Python tr

[issue5096] strange thing after call PyObject_CallMethod

Amaury Forgeot d'Arc 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 explains why frame_deallo

[issue5096] strange thing after call PyObject_CallMethod

New submission from Kandalintsev Alexandre : 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 both this functions doin