Lines Matching refs:Py_Finalize

8378 - Issue #10363: Deallocate global locks in Py_Finalize().
11905 - Issue #9901: Destroying the GIL in Py_Finalize() can fail if some other
11925 - Issue #9828: Destroy the GIL in Py_Finalize(), so that it gets properly
12976 - Issue #1722344: threading._shutdown() is now called in Py_Finalize(), which
20495 - At Python shutdown time (Py_Finalize()), 2.3 called cyclic garbage
21301   use.  The interpreter now calls WSACleanup() from Py_Finalize()
30210 - Changed the checks made in Py_Initialize() and Py_Finalize().  It is
30212 Py_Initialize() initializes, the first call to Py_Finalize()
31302 - There is now a Py_Finalize() function which "de-initializes"
31304 repeatedly by calling Py_Finalize() followed by Py_Initialize().  A
31308 is deprecated (it is nothing more than Py_Finalize() followed by
31311 - There are no known memory leaks left.  While Py_Finalize() doesn't
31313 repeated calls to Py_Finalize() and Py_Initialize() do not create