[PyPy-issue] [issue586] Show a traceback when an exception is raised in a destructor
Dan Villiom Podlaski Christiansen
pypy-dev-issue at codespeak.net
Wed Dec 1 22:04:42 CET 2010
New submission from Dan Villiom Podlaski Christiansen <danchr at gmail.com>:
When an exception is raised in a destructor, PyPy currently prints a message like this:
a destructor raised an exception, ignoring it
Other than the fact that the word “was” seems to have been left out, this isn't terribly helpful. It doesn't say
anything about the exception that was raised. Either printing a traceback or the destructor that failed
would be a vast improvement. I think that's what CPython does.
I tried reproducing this with a small test script, but it actually printed the destructor that failed. However,
this isn't what I'm seeing in one of the remaining failures in Mercurial test suite.
----------
effort: ???
messages: 1914
nosy: danchr, pypy-issue
priority: feature
release: 1.4
status: unread
title: Show a traceback when an exception is raised in a destructor
_______________________________________________________
PyPy development tracker <pypy-dev-issue at codespeak.net>
<https://codespeak.net/issue/pypy-dev/issue586>
_______________________________________________________
More information about the Pypy-issue
mailing list