bpo-38304: PyConfig_InitPythonConfig() cannot fail anymore (GH-16509)
PyConfig_InitPythonConfig() and PyConfig_InitIsolatedConfig() no
longer return PyStatus: they cannot fail anymore.
(cherry picked from commit 8462a4936b3a551dc546a6adea04a70b0a07ca67)
Co-authored-by: Victor Stinner <vstinner@redhat.com>
diff --git a/Python/pystate.c b/Python/pystate.c
index 098280d..aba673c 100644
--- a/Python/pystate.c
+++ b/Python/pystate.c
@@ -206,14 +206,7 @@
interp->id_refcount = -1;
interp->check_interval = 100;
- PyStatus status = PyConfig_InitPythonConfig(&interp->config);
- if (_PyStatus_EXCEPTION(status)) {
- /* Don't report status to caller: PyConfig_InitPythonConfig()
- can only fail with a memory allocation error. */
- PyConfig_Clear(&interp->config);
- PyMem_RawFree(interp);
- return NULL;
- }
+ PyConfig_InitPythonConfig(&interp->config);
interp->eval_frame = _PyEval_EvalFrameDefault;
#ifdef HAVE_DLOPEN