➜

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 abarry
Recipients abarry, matrixise, ncoghlan, serhiy.storchaka, vstinner, yselivanov
Date 2016-10-18.15:52:39
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1476805959.16.0.491261600062.issue28410@psf.upfronthosting.co.za>
In-reply-to
Content 
I see the function is private; is there any concern with extending the PyErr_* API? I think it'd make sense to expose it, since it's a convenient way to do in C what can already be done easily in Python, but I don't actually have a good reason :)

Other than this small nitpick, this LGTM.

(Alternatively, we can keep it private for 3.6 and revise that decision for 3.7)
History
Date User Action Args
2016-10-18 15:52:39abarrysetrecipients: + abarry, ncoghlan, vstinner, serhiy.storchaka, yselivanov, matrixise
2016-10-18 15:52:39abarrysetmessageid: <1476805959.16.0.491261600062.issue28410@psf.upfronthosting.co.za>
2016-10-18 15:52:39abarrylinkissue28410 messages
2016-10-18 15:52:39abarrycreate