[PyPy-issue] [issue586] Show a traceback when an exception is raised in a destructor

Carl Friedrich Bolz pypy-dev-issue at codespeak.net
Thu Dec 2 13:53:01 CET 2010


Carl Friedrich Bolz <cfbolz at gmx.de> added the comment:

This is quite likely a bug in PyPy that is just reported very
unhelpfully. Probably one of the interpreter-level destructors raised
something, e.g. files or similar. In this case writing the traceback
wouldn't help either, because there is none on the RPython level. Maybe
I can try to improve things so that at least some more information is
printed.

----------
status: unread -> chatting

_______________________________________________________
PyPy development tracker <pypy-dev-issue at codespeak.net>
<https://codespeak.net/issue/pypy-dev/issue586>
_______________________________________________________



More information about the Pypy-issue mailing list