The deprecation of Python’s PyEval_ReleaseLock has introduced a problem in our codebase: We want to terminate a Python interpreter from a C callback function using Py_EndInterpreter So to do that,, superseder: test_threading: test_threads_join_2() failed with Fatal Python error: Py_EndInterpreter: not the last thread resolution: duplicate: 2016-09-11 21:24:58: christian.heimes: create, 2/5/2006 · Fatal Python error: Py_ EndInterpreter: thread still has a frame does occur. I checked the source code of pythonrun.c, which tells me that this error message is thrown in Py_EndInterpreter, when thread->frame is checked for being NULL. Does anyone know, when this pointer is not NULL at the time where Py_EndInterpreter() is called?, Py_EndInterpreter(PyThreadState *tstate) { PyInterpreterState *interp = tstate->interp if (tstate != PyThreadState_GET()) Py_FatalError(Py_EndInterpreter: thread is not current) if (tstate->frame != NULL) Py_FatalError(Py_EndInterpreter: thread still has a frame) if (tstate != interp->tstate_head || tstate->next != NULL) Py_FatalError(Py_EndInterpreter: not the last thread) PyImport_Cleanup().
void Py_EndInterpreter (PyThreadState *tstate) ¶ Destroy the (sub-)interpreter represented by the given thread state. The given thread state must be the current thread state. See the discussion of thread states below. When the call returns, the current thread state is NULL. All thread states associated with this interpreter are destroyed.
Py_EndInterpreter() now clears the filesystem codec. vstinner force-pushed the vstinner:unicode_fini branch from 2c05832 to 5705064 Nov 22, 2019 This comment has been minimized.
4/30/2020 · In the main it creates instance python controller and initialize python using PythonRunner class and its Initialize method. Then (case 0) there is loop in the main where it creates 2 independent python executors in their own c++ threads and with their own python interpreters using PythonRunner::addExecutor method.
10/20/2016 · Py_EndInterpreter ( pThreadState ) PyEval_ReleaseLock () return 0 } Once the worker thread has created its interpreter, it runs a short loop, swapping the interpreter in, running a bit of Python code (just a simple print statement), then swapping the.
Py_EndInterpreter() shares almost all its code with Py_Finalizer(). It’s not perfect, but it’s way better than previously. Py_NewInterpreter() now isolates more things from the main interpreter.
Loop over subinterpreters in Py_FinalizeEx() and call Py_EndInterpreter() New flag _PyRuntime.interpreters.allow_new to prevent new subinterpreters from being created during finalisation Error if calling Py_FinalizeEx() from a subinterpreter (to be changed at a later stage) https://bugs.python.org/issue36225. Also addresses bpo-38865 and bpo-37776.
