Message124643
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. |
|
Date |
User |
Action |
Args |
2010-12-25 17:20:23 | Trundle | set | recipients:
+ Trundle, mark.dickinson, kaizhu |
2010-12-25 17:20:23 | Trundle | set | messageid: <1293297623.07.0.705471898091.issue10756@psf.upfronthosting.co.za> |
2010-12-25 17:20:19 | Trundle | link | issue10756 messages |
2010-12-25 17:20:19 | Trundle | create | |
|