#5753: update demo.c to use PySys_SetArgvEx(), and add a comment
This commit is contained in:
parent
a0b0c6f23c
commit
de0aeaa432
|
@ -16,10 +16,19 @@ main(int argc, char **argv)
|
||||||
initxyzzy();
|
initxyzzy();
|
||||||
|
|
||||||
/* Define sys.argv. It is up to the application if you
|
/* Define sys.argv. It is up to the application if you
|
||||||
want this; you can also let it undefined (since the Python
|
want this; you can also leave it undefined (since the Python
|
||||||
code is generally not a main program it has no business
|
code is generally not a main program it has no business
|
||||||
touching sys.argv...) */
|
touching sys.argv...)
|
||||||
PySys_SetArgv(argc, argv);
|
|
||||||
|
If the third argument is true, sys.path is modified to include
|
||||||
|
either the directory containing the script named by argv[0], or
|
||||||
|
the current working directory. This can be risky; if you run
|
||||||
|
an application embedding Python in a directory controlled by
|
||||||
|
someone else, attackers could put a Trojan-horse module in the
|
||||||
|
directory (say, a file named os.py) that your application would
|
||||||
|
then import and run.
|
||||||
|
*/
|
||||||
|
PySys_SetArgvEx(argc, argv, 0);
|
||||||
|
|
||||||
/* Do some application specific code */
|
/* Do some application specific code */
|
||||||
printf("Hello, brave new world\n\n");
|
printf("Hello, brave new world\n\n");
|
||||||
|
|
Loading…
Reference in New Issue