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 Maxime Belanger
Recipients Maxime Belanger
Date 2021-03-02.20:42:16
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1614717737.06.0.355391552087.issue43377@roundup.psfhosted.org>
In-reply-to
Content
We have found `_PyErr_Display` to be quite helpful in embedding situations, in particular as a way to capture errors to a custom buffer rather than to `stderr`. Otherwise, embedders often have to replicate logic in `PyErr_Print`, etc. 

Since the header restructuring in Python 3.8+, that function is a bit harder to call. It's exported, but is considered "internal" and thus requires defining `Py_BUILD_CORE`.

I was wondering: why not expose it under "Include/cpython"? It seems like a generic-enough helper, similar to `_PyErr_WriteUnraisableMsg`.
History
Date User Action Args
2021-03-02 20:42:17Maxime Belangersetrecipients: + Maxime Belanger
2021-03-02 20:42:17Maxime Belangersetmessageid: <1614717737.06.0.355391552087.issue43377@roundup.psfhosted.org>
2021-03-02 20:42:17Maxime Belangerlinkissue43377 messages
2021-03-02 20:42:16Maxime Belangercreate