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 scoder
Recipients Jim.Jewett, Mark.Shannon, amaury.forgeotdarc, benjamin.peterson, jcea, ncoghlan, pitrou, ron_adam, scoder
Date 2012-04-14.09:16:12
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
>> As long as there is a way to access these fields directly from the
>> struct (with the usual preprocessor conditional), I don't think Cython
>> will actually start to use the PyErr_[GS]etExcInfo() functions in
>> CPython - simply for performance reasons.
> Isn't this premature optimization? Do you have any workload where you
> measured a performance degradation?

To be honest - I don't know if it makes a measurable difference. However, the code is there, it's required for all currently released CPython versions (i.e. those still being supported for years to come), and it is used in seriously performance critical places, such as each generator/coroutine iteration - twice. Why should we add overhead to those without need?
Date User Action Args
2012-04-14 09:16:13scodersetrecipients: + scoder, jcea, amaury.forgeotdarc, ncoghlan, pitrou, ron_adam, benjamin.peterson, Mark.Shannon, Jim.Jewett
2012-04-14 09:16:13scodersetmessageid: <>
2012-04-14 09:16:12scoderlinkissue13897 messages
2012-04-14 09:16:12scodercreate