➜

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 vstinner
Recipients Dennis Sweeney, SD, eryksun, lunixbochs2, miss-islington, ned.deily, pablogsal, paul.moore, pitrou, steve.dower, tim.golden, vstinner, zach.ware
Date 2021-09-24.13:52:21
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1632491542.05.0.958540641883.issue41299@roundup.psfhosted.org>
In-reply-to
Content 
Calling Py_FatalError() must be avoided by any mean. I spent significant time to remove Py_FatalError() at Python startup in my PEP 587 implementation: https://www.python.org/dev/peps/pep-0587/

I also removed Py_FatalError() calls to report errors to the caller: https://bugs.python.org/issue38631

Calling Py_FatalError() is really bad when Python is embedded in an application. It kills the whole process, the caller has no way to catch the error.
History
Date User Action Args
2021-09-24 13:52:22vstinnersetrecipients: + vstinner, paul.moore, pitrou, tim.golden, ned.deily, zach.ware, eryksun, steve.dower, pablogsal, miss-islington, Dennis Sweeney, SD, lunixbochs2
2021-09-24 13:52:22vstinnersetmessageid: <1632491542.05.0.958540641883.issue41299@roundup.psfhosted.org>
2021-09-24 13:52:22vstinnerlinkissue41299 messages
2021-09-24 13:52:21vstinnercreate