Message233625
| Author | ncoghlan |
|---|---|
| Recipients | ncoghlan |
| Date | 2015-01-08.08:18:39 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1420705119.75.0.567862927059.issue23188@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
After looking into this further, PyErr_SetObject (and other APIs like PyErr_SetString which call that internally) aim to handle the chaining automatically, but they don't handle exceptions which haven't been normalized yet. PyErr_SetObject should probably normalise the exception at the start of the call f ithe exception type is set on the thread state, but not the exception value. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2015-01-08 08:18:39 | ncoghlan | set | recipients: + ncoghlan |
| 2015-01-08 08:18:39 | ncoghlan | set | messageid: <1420705119.75.0.567862927059.issue23188@psf.upfronthosting.co.za> |
| 2015-01-08 08:18:39 | ncoghlan | link | issue23188 messages |
| 2015-01-08 08:18:39 | ncoghlan | create | |