Message231855
Ah, right - chaining only happens automatically when the exception has already been caught and moved to sys.exc_info.
There's a _PyErr_ChainExceptions(), though, which does it for you. You should be able to say
PyErr_Fetch(&x,&y,&z)
PyErr_SetString()
_PyErr_ChainExceptions(x,y,z)
(does pretty much what your code does as well) |
|
Date |
User |
Action |
Args |
2014-11-29 08:59:59 | scoder | set | recipients:
+ scoder, gvanrossum, rhettinger, belopolsky, vstinner, r.david.murray, python-dev, schlamar, Rosuav, serhiy.storchaka |
2014-11-29 08:59:59 | scoder | set | messageid: <1417251599.76.0.91840106708.issue22906@psf.upfronthosting.co.za> |
2014-11-29 08:59:59 | scoder | link | issue22906 messages |
2014-11-29 08:59:59 | scoder | create | |
|