bpo-46008: Return void from _PyEval_InitState(). (gh-29970)

This falls into the category of keep-allocation-and-initialization separate. It also allows us to use _PyEval_InitState() safely in functions that return void.

https://bugs.python.org/issue46008
This commit is contained in:
Eric Snow 2021-12-07 14:02:17 -07:00 committed by GitHub
parent 91b59a3fcd
commit 8262c96bcc
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
3 changed files with 7 additions and 10 deletions

View file

@ -225,10 +225,12 @@ PyInterpreterState_New(void)
_PyRuntimeState *runtime = &_PyRuntime;
interp->runtime = runtime;
if (_PyEval_InitState(&interp->ceval) < 0) {
PyThread_type_lock pending_lock = PyThread_allocate_lock();
if (pending_lock == NULL) {
goto out_of_memory;
}
_PyEval_InitState(&interp->ceval, pending_lock);
_PyGC_InitState(&interp->gc);
PyConfig_InitPythonConfig(&interp->config);
_PyType_InitCache(interp);