[issue5096] strange thing after call PyObject_CallMethod
Kandalintsev Alexandre
report at bugs.python.org
Thu Jan 29 12:42:55 CET 2009
New submission from Kandalintsev Alexandre <bug_hunter at 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 both
this functions doing same work(http://docs.python.org/3.0/c-api/
exceptions.html). As we see thats not true or not all nuances documented.
Examples and more on this mailing list:
http://groups.google.com/group/comp.lang.python/browse_thread/
thread/19316b3effa37d2d
----------
components: Interpreter Core
messages: 80757
nosy: exe
severity: normal
status: open
title: strange thing after call PyObject_CallMethod
type: behavior
versions: Python 3.0, Python 3.1
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue5096>
_______________________________________
More information about the Python-bugs-list
mailing list