➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ronaldoussoren
Recipients amaury.forgeotdarc, loewis, pitrou, python-dev, ronaldoussoren, scoder
Date 2012-04-19.14:11:25
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1334844685.96.0.46678694309.issue14098@psf.upfronthosting.co.za>
In-reply-to
Content 
The documentation does not explain how this new API is different from PyErr_Fetch/PyErr_Restore.  In particular the documentation doesn't mention that PyErr_Fetch and PyErr_GetExcInfo access different bits of the error state (curexc_* vs. exc_* in the thread state). 

Because of this it is not clear why there are two sets of functions, and why you want to use one set or the other.
History
Date User Action Args
2012-04-19 14:11:26ronaldoussorensetrecipients: + ronaldoussoren, loewis, amaury.forgeotdarc, pitrou, scoder, python-dev
2012-04-19 14:11:25ronaldoussorensetmessageid: <1334844685.96.0.46678694309.issue14098@psf.upfronthosting.co.za>
2012-04-19 14:11:25ronaldoussorenlinkissue14098 messages
2012-04-19 14:11:25ronaldoussorencreate