|
Original |
Translation |
|
9
|
|
|
|
10
|
The interpreter interface resembles that of the UNIX shell, but provides some additional methods of invocation:
|
|
|
11
|
When called with standard input connected to a tty device, it prompts for commands and executes them until an EOF (an end-of-file character, you can produce that with *Ctrl-D* on UNIX or *Ctrl-Z, Enter* on Windows) is read.
|
|
|
12
|
When called with a file name argument or with a file as standard input, it reads and executes a script from that file.
|
|
|
13
|
|
14
|
When called with ``-c command``, it executes the Python statement(s) given as *command*. Here *command* may contain multiple statements separated by newlines. Leading whitespace is significant in Python statements!
|
|
|
15
|
When called with ``-m module-name``, the given module is located on the Python module path and executed as a script.
|
|
|
16
|
In non-interactive mode, the entire input is parsed before it is executed.
|
|
|
17
|
An interface option terminates the list of options consumed by the interpreter, all consecutive arguments will end up in :data:`sys.argv` -- note that the first element, subscript zero (``sys.argv[0]``), is a string reflecting the program's source.
|
|
|
18
|
Execute the Python code in *command*. *command* can be one ore more statements separated by newlines, with significant leading whitespace as in normal module code.
|
|