-
-
Notifications
You must be signed in to change notification settings - Fork 32.2k
gh-80406: Finalise subinterpreters in Py_FinalizeEx() #17575
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Changes from all commits
23af5f5
433663c
48e1cfc
0400634
b79649c
8b1e7d9
fd6073a
4bbd58f
1095e66
675285d
8e21788
606c068
e0789b0
dda99ce
847e8d2
a2fb0fc
d234528
46a8619
c89c0e5
c285f52
95cbfd4
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1 @@ | ||
:func:`Py_FinalizeEx()` now implicitly cleans up subinterpreters, as the C API documentation suggests. |
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -16,7 +16,7 @@ | |
/********************************************************* | ||
* Embedded interpreter tests that need a custom exe | ||
* | ||
* Executed via 'EmbeddingTests' in Lib/test/test_capi.py | ||
* Executed via 'EmbeddingTests' in Lib/test/test_embed.py | ||
*********************************************************/ | ||
|
||
/* Use path starting with "./" avoids a search along the PATH */ | ||
|
@@ -83,6 +83,60 @@ static int test_repeated_init_and_subinterpreters(void) | |
return 0; | ||
} | ||
|
||
/* bpo-36225: Implicitly tear down subinterpreters with Py_Finalize() */ | ||
static int test_finalize_subinterps(void) | ||
{ | ||
PyThreadState *mainstate; | ||
PyThreadState *interp_tstate; | ||
PyGILState_STATE gilstate; | ||
int i; | ||
|
||
_testembed_Py_Initialize(); | ||
mainstate = PyThreadState_Get(); | ||
|
||
PyEval_ReleaseThread(mainstate); | ||
|
||
gilstate = PyGILState_Ensure(); | ||
print_subinterp(); | ||
PyThreadState_Swap(NULL); | ||
|
||
// Create 3 subinterpreters and destroy the last one. | ||
for (i=0; i<3; i++) { | ||
interp_tstate = Py_NewInterpreter(); | ||
print_subinterp(); | ||
} | ||
PyThreadState_Swap(interp_tstate); | ||
Py_EndInterpreter(interp_tstate); | ||
|
||
// Switch back to the main interpreter and finalize the runtime. | ||
PyThreadState_Swap(mainstate); | ||
print_subinterp(); | ||
PyGILState_Release(gilstate); | ||
|
||
PyEval_RestoreThread(mainstate); | ||
Py_Finalize(); | ||
|
||
return 0; | ||
} | ||
|
||
/* bpo-38865: Py_Finalize() should not be called from a subinterpreter */ | ||
static int test_finalize_from_subinterp(void) | ||
{ | ||
PyThreadState *subinterp_tstate; | ||
int rc; | ||
|
||
_testembed_Py_Initialize(); | ||
PyGILState_Ensure(); | ||
PyThreadState_Swap(NULL); | ||
|
||
subinterp_tstate = Py_NewInterpreter(); | ||
PyThreadState_Swap(subinterp_tstate); | ||
|
||
rc = Py_FinalizeEx(); | ||
|
||
return rc; | ||
} | ||
|
||
/***************************************************** | ||
* Test forcing a particular IO encoding | ||
*****************************************************/ | ||
|
@@ -1195,10 +1249,14 @@ static int test_audit_subinterpreter(void) | |
PySys_AddAuditHook(_audit_subinterpreter_hook, NULL); | ||
_testembed_Py_Initialize(); | ||
|
||
PyThreadState *mainstate = PyThreadState_Get(); | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. You may want to double-check with @zooba on his intention here. It's pretty important to make sure that the auditing functionality works as expected. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Hi @zooba, as a consequence of my changes here, The change I'm making is to make In the test, multiple subinterpreters are created, and then The test passes if There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. See #19063 from @vstinner which was not merged, but also proposed to change the logic of this testcase. It seems like this testcase is doing something that is not currently working, and according to bpo-38865#msg357331 may not be supported in general? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I also confirmed that this test still fails on my branch without this change. |
||
|
||
Py_NewInterpreter(); | ||
Py_NewInterpreter(); | ||
Py_NewInterpreter(); | ||
|
||
// Currently unable to call Py_Finalize from subinterpreter thread, see bpo-37776. | ||
PyThreadState_Swap(mainstate); | ||
Py_Finalize(); | ||
|
||
switch (_audit_subinterpreter_interpreter_count) { | ||
|
@@ -1707,6 +1765,8 @@ struct TestCase | |
static struct TestCase TestCases[] = { | ||
{"test_forced_io_encoding", test_forced_io_encoding}, | ||
{"test_repeated_init_and_subinterpreters", test_repeated_init_and_subinterpreters}, | ||
{"test_finalize_subinterps", test_finalize_subinterps}, | ||
LewisGaul marked this conversation as resolved.
Show resolved
Hide resolved
|
||
{"test_finalize_from_subinterp", test_finalize_from_subinterp}, | ||
{"test_pre_initialization_api", test_pre_initialization_api}, | ||
{"test_pre_initialization_sys_options", test_pre_initialization_sys_options}, | ||
{"test_bpo20891", test_bpo20891}, | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -76,6 +76,7 @@ _PyRuntime_Initialize(void) | |
return _PyStatus_OK(); | ||
} | ||
runtime_initialized = 1; | ||
_PyRuntime.interpreters.allow_new = 0; | ||
|
||
return _PyRuntimeState_Init(&_PyRuntime); | ||
} | ||
|
@@ -1015,6 +1016,7 @@ init_interp_main(PyThreadState *tstate) | |
*/ | ||
if (is_main_interp) { | ||
interp->runtime->initialized = 1; | ||
interp->runtime->interpreters.allow_new = 1; | ||
} | ||
return _PyStatus_OK(); | ||
} | ||
|
@@ -1086,6 +1088,7 @@ init_interp_main(PyThreadState *tstate) | |
} | ||
|
||
interp->runtime->initialized = 1; | ||
interp->runtime->interpreters.allow_new = 1; | ||
} | ||
|
||
if (config->site_import) { | ||
|
@@ -1646,6 +1649,42 @@ Py_FinalizeEx(void) | |
|
||
/* Get current thread state and interpreter pointer */ | ||
PyThreadState *tstate = _PyRuntimeState_GetThreadState(runtime); | ||
PyInterpreterState *interp = tstate->interp; | ||
|
||
/* Check we're running in the main interpreter (not yet supported to call | ||
* from any interpreter). | ||
*/ | ||
if (interp != PyInterpreterState_Main()) { | ||
Py_FatalError("must be called from the main interpreter\n"); | ||
} | ||
|
||
// Finalize sub-interpreters. | ||
PyThread_acquire_lock(runtime->interpreters.mutex, WAIT_LOCK); | ||
runtime->interpreters.allow_new = 0; | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. It may be safer to acquire _PyRuntime.interpreters.mutex beforing setting this variable. It may be better to move this code into pystate.c, since this file control the list of interpreters. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I presume you're suggesting refactoring the 'finalize subinterpreters' logic? It would seem to me a function that does 'finalizing' belongs better in pylifecycle than pystate? I believe this refactoring was referred to by Eric above, where he says this can be addressed separately. I've added in an acquisition of the lock here for now. |
||
PyThread_release_lock(runtime->interpreters.mutex); | ||
PyInterpreterState *curr_interp = PyInterpreterState_Head(); | ||
PyInterpreterState *next_interp; | ||
int64_t num_destroyed = 0; | ||
while (curr_interp != NULL) { | ||
next_interp = PyInterpreterState_Next(curr_interp); | ||
if (curr_interp != interp) { | ||
PyThreadState_Swap(curr_interp->tstate_head); | ||
Py_EndInterpreter(curr_interp->tstate_head); | ||
num_destroyed++; | ||
} | ||
curr_interp = next_interp; | ||
} | ||
PyThreadState_Swap(tstate); | ||
|
||
if (num_destroyed > 0) { | ||
/* Sub-interpreters were still running, but should have be finalized | ||
* before finalizing the runtime. | ||
*/ | ||
if (PyErr_ResourceWarning(NULL, 1, | ||
"extra %zd interpreters", num_destroyed)) { | ||
LewisGaul marked this conversation as resolved.
Show resolved
Hide resolved
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I'm not sure why, but for some reason this warning isn't being output in the tests on Windows only. Anyone have any ideas? |
||
_PyErr_WriteUnraisableMsg("in PyFinalizeEx", NULL); | ||
} | ||
} | ||
|
||
// Wrap up existing "threading"-module-created, non-daemon threads. | ||
wait_for_thread_shutdown(tstate); | ||
|
@@ -1668,13 +1707,13 @@ Py_FinalizeEx(void) | |
/* Copy the core config, PyInterpreterState_Delete() free | ||
the core config memory */ | ||
#ifdef Py_REF_DEBUG | ||
int show_ref_count = tstate->interp->config.show_ref_count; | ||
int show_ref_count = interp->config.show_ref_count; | ||
#endif | ||
#ifdef Py_TRACE_REFS | ||
int dump_refs = tstate->interp->config.dump_refs; | ||
int dump_refs = interp->config.dump_refs; | ||
#endif | ||
#ifdef WITH_PYMALLOC | ||
int malloc_stats = tstate->interp->config.malloc_stats; | ||
int malloc_stats = interp->config.malloc_stats; | ||
#endif | ||
|
||
/* Remaining daemon threads will automatically exit | ||
|
@@ -1833,8 +1872,10 @@ new_interpreter(PyThreadState **tstate_p, int isolated_subinterpreter) | |
} | ||
_PyRuntimeState *runtime = &_PyRuntime; | ||
|
||
if (!runtime->initialized) { | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I'd not remove this condition There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Sorry for any confusion, @soltysh. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @ericsnowcurrently so runtime is always a single object (like an uber-object) and then you can create multiple interpreters. Right, but that still requires the runtime to be initialized. Even though the situation should not happen, because I'd assume the first invocation of python would initialize the runtime, it should not hurt having this here. Unless my thinking is wrong here. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I suppose your suggestion @soltysh would be to have two separate checks on It's a while ago now, but I think my reasoning here was that this 'allow_new' flag encapsulates all information about whether a new interpreter can be created, so there should be no need to check things like whether the runtime is initialised (since 'allow_new' is only set to true when the runtime is initialised). Does that sounds reasonable? I could be persuaded to change this if there are better suggestions :) |
||
return _PyStatus_ERR("Py_Initialize must be called first"); | ||
if (!runtime->interpreters.allow_new) { | ||
return _PyStatus_ERR( | ||
"New interpreters cannot currently be created - Py_Initialize must " | ||
"be called first, and Py_Finalize must not have been called"); | ||
} | ||
|
||
/* Issue #10915, #15751: The GIL API doesn't work with multiple | ||
|
Uh oh!
There was an error while loading. Please reload this page.