Message 80757 - Python tracker

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author	exe
Recipients	exe
Date	2009-01-29.11:42:53
SpamBayes Score	0.00047657153
Marked as misclassified	No
Message-id	<1233229375.88.0.463699429869.issue5096@psf.upfronthosting.co.za>
In-reply-to

Content
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

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

History
Date	User	Action	Args
2009-01-29 11:42:55	exe	set	recipients: + exe
2009-01-29 11:42:55	exe	set	messageid: <1233229375.88.0.463699429869.issue5096@psf.upfronthosting.co.za>
2009-01-29 11:42:54	exe	link	issue5096 messages
2009-01-29 11:42:53	exe	create