From: Sandro Tosi Date: Sat, 7 Jan 2012 17:32:06 +0000 (+0100) Subject: Py_SetPythonHome() can be called before Py_Initialize(); thanks to Cody Smith from... X-Git-Tag: v2.7.3rc1~187 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=e5f93ef268bec844159ae84ac91f9aa46d987729;p=python Py_SetPythonHome() can be called before Py_Initialize(); thanks to Cody Smith from docs@ --- diff --git a/Doc/c-api/init.rst b/Doc/c-api/init.rst index c323eef4cf..a53b4945ad 100644 --- a/Doc/c-api/init.rst +++ b/Doc/c-api/init.rst @@ -31,7 +31,7 @@ Initializing and finalizing the interpreter Initialize the Python interpreter. In an application embedding Python, this should be called before using any other Python/C API functions; with the - exception of :cfunc:`Py_SetProgramName`, :cfunc:`PyEval_InitThreads`, + exception of :cfunc:`Py_SetProgramName`, :cfunc:`Py_SetPythonHome`, :cfunc:`PyEval_InitThreads`, :cfunc:`PyEval_ReleaseLock`, and :cfunc:`PyEval_AcquireLock`. This initializes the table of loaded modules (``sys.modules``), and creates the fundamental modules :mod:`__builtin__`, :mod:`__main__` and :mod:`sys`. It also initializes