From: Andrew M. Kuchling Date: Fri, 11 Jun 2010 00:23:01 +0000 (+0000) Subject: #5753: Suggest PySys_SetArgvEx() instead of PySys_SetArgv() X-Git-Tag: v2.7rc2~39 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=81145c9b1d781c11b42f48a6e8706597e4bfdcd9;p=python #5753: Suggest PySys_SetArgvEx() instead of PySys_SetArgv() --- diff --git a/Doc/c-api/intro.rst b/Doc/c-api/intro.rst index c56000efa4..5ea6dd303c 100644 --- a/Doc/c-api/intro.rst +++ b/Doc/c-api/intro.rst @@ -524,12 +524,12 @@ the table of loaded modules, and creates the fundamental modules :mod:`__builtin__`, :mod:`__main__`, :mod:`sys`, and :mod:`exceptions`. It also initializes the module search path (``sys.path``). -.. index:: single: PySys_SetArgv() +.. index:: single: PySys_SetArgvEx() :cfunc:`Py_Initialize` does not set the "script argument list" (``sys.argv``). -If this variable is needed by Python code that will be executed later, it must -be set explicitly with a call to ``PySys_SetArgv(argc, argv)`` subsequent to -the call to :cfunc:`Py_Initialize`. +If this variable is needed by Python code that will be executed later, it must +be set explicitly with a call to ``PySys_SetArgvEx(argc, argv, updatepath)`` +after the call to :cfunc:`Py_Initialize`. On most systems (in particular, on Unix and Windows, although the details are slightly different), :cfunc:`Py_Initialize` calculates the module search path