public@colinux 3 ~: python3.2
Python 3.2b2 (py3k, Dec 22 2010, 02:38:55) 
[GCC 4.4.5] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import atexit; atexit.register(lambda:1/0)
<function <lambda> at 0xb7c7e12c>
>>> exit()
Error in atexit._run_exitfuncs:
TypeError: print_exception(): Exception expected for value, str found



might b related to Issue5089, so included those ppl to nosy.  this bug is subtle.  unit tests which explicitly 'raise' exceptions will not b caught, e.g. this will raise properly:

@exit.register
def foo(): raise ZeroDivisionError()

It's because `PyErr_Fetch()` which is used in `atexit_callfuncs()` can return an unnormalized exception (e.g. if the exception is set with `PyErr_SetString()`. "value" is then a string). A simple call to `PyErr_NormalizeException()` fixes this issue.

Attached is a patch which fixes the issue and adds a test for it. I used exactly the same code ("1 / 0") to raise the exception, as I don't know if there is some clean way to raise an unnormalized exception.

Looks good to me.  I’d just move the raising function into the test method (no need to update the patch).

+1.

So I guess someone should feel responsible and commit that patch. For convenience, I updated the patch to inline the raise.

I think Antoine might be interested.

Commited as r87755+r87758. Wait for the buildbot before backporting to other versions.

should this bug b closed? it seems fixed in python3.2 for me.

Well, Victor still wanted to backport it.

New changeset 461e37a60187 by Victor Stinner in branch '3.1':
Issue #10756: atexit normalizes the exception before displaying it. Patch by
http://hg.python.org/cpython/rev/461e37a60187

Oh, I forgot the issue. I backported the fix to Python 3.1. Python 2.7 doesn't have the bug.