bpo-33877: Remove UNIX qualification for running complete programs (GH-7744)
The statement is true for Windows (and macOS) also.
(cherry picked from commit c9d43c702a
)
Co-authored-by: Andrés Delfino <adelfino@gmail.com>
This commit is contained in:
parent
e4db73058b
commit
f47d8983fe
|
@ -48,14 +48,15 @@ a complete program; each statement is executed in the namespace of
|
||||||
|
|
||||||
.. index::
|
.. index::
|
||||||
single: UNIX
|
single: UNIX
|
||||||
|
single: Windows
|
||||||
single: command line
|
single: command line
|
||||||
single: standard input
|
single: standard input
|
||||||
|
|
||||||
Under Unix, a complete program can be passed to the interpreter in three forms:
|
A complete program can be passed to the interpreter
|
||||||
with the :option:`-c` *string* command line option, as a file passed as the
|
in three forms: with the :option:`-c` *string* command line option, as a file
|
||||||
first command line argument, or as standard input. If the file or standard
|
passed as the first command line argument, or as standard input. If the file
|
||||||
input is a tty device, the interpreter enters interactive mode; otherwise, it
|
or standard input is a tty device, the interpreter enters interactive mode;
|
||||||
executes the file as a complete program.
|
otherwise, it executes the file as a complete program.
|
||||||
|
|
||||||
|
|
||||||
.. _file-input:
|
.. _file-input:
|
||||||
|
|
Loading…
Reference in New Issue