Message 355651 - Python tracker

➜

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	vstinner
Date	2019-10-29.12:38:55
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1572352735.51.0.915792481752.issue38631@roundup.psfhosted.org>
In-reply-to

Content
I replaced dozens of Py_FatalError() calls with better error reporting, but there are still many places calling Py_FatalError(). The problem of Py_FatalError() is when Python is embedded into an application: Python must not kill the whole process. Well, even in the "regular" Python (/usr/bin/python3), Python should not exit immediately on an error. For example, the readline module calls Py_FatalError() on memory allocation failure, whereas PyErr_NoMemory() could be used: PyErr_NoMemory() should work since it should not allocate memory.

I replaced dozens of Py_FatalError() calls with better error reporting, but there are still many places calling Py_FatalError().

The problem of Py_FatalError() is when Python is embedded into an application: Python must not kill the whole process.

Well, even in the "regular" Python (/usr/bin/python3), Python should not exit immediately on an error.

For example, the readline module calls Py_FatalError() on memory allocation failure, whereas PyErr_NoMemory() could be used: PyErr_NoMemory() should work since it should not allocate memory.

History
Date	User	Action	Args
2019-10-29 12:38:55	vstinner	set	recipients: + vstinner
2019-10-29 12:38:55	vstinner	set	messageid: <1572352735.51.0.915792481752.issue38631@roundup.psfhosted.org>
2019-10-29 12:38:55	vstinner	link	issue38631 messages
2019-10-29 12:38:55	vstinner	create