Update the description of how to start an interpreter and determine the
installation prefix and exec_prefix for Windows.
This commit is contained in:
parent
b4b64daa5e
commit
b2d1006272
|
@ -361,12 +361,13 @@ run-time. They are always the same under Windows and MacOS, and very
|
||||||
often the same under \UNIX. You can find out what your Python
|
often the same under \UNIX. You can find out what your Python
|
||||||
installation uses for \filevar{prefix} and \filevar{exec-prefix} by
|
installation uses for \filevar{prefix} and \filevar{exec-prefix} by
|
||||||
running Python in interactive mode and typing a few simple commands.
|
running Python in interactive mode and typing a few simple commands.
|
||||||
Under \UNIX, just type \code{python} at the shell prompt; under Windows,
|
Under \UNIX, just type \code{python} at the shell prompt. Under
|
||||||
run ``Python 2.0 (interpreter)'' \XXX{right?}; under MacOS, \XXX{???}.
|
Windows, choose \menuselection{Start \sub Programs \sub Python
|
||||||
|
2.1 \sub Python (command line)}. Under MacOS, \XXX{???}.
|
||||||
Once the interpreter is started, you type Python code at the
|
Once the interpreter is started, you type Python code at the
|
||||||
\samp{>\code{>}> } prompt. For example, on my Linux system, I type the three
|
prompt. For example, on my Linux system, I type the three Python
|
||||||
Python statements shown below, and get the output as shown, to find
|
statements shown below, and get the output as shown, to find out my
|
||||||
out my \filevar{prefix} and \filevar{exec-prefix}:
|
\filevar{prefix} and \filevar{exec-prefix}:
|
||||||
|
|
||||||
\begin{verbatim}
|
\begin{verbatim}
|
||||||
Python 1.5.2 (#1, Apr 18 1999, 16:03:16) [GCC pgcc-2.91.60 19981201 (egcs-1.1.1 on linux2
|
Python 1.5.2 (#1, Apr 18 1999, 16:03:16) [GCC pgcc-2.91.60 19981201 (egcs-1.1.1 on linux2
|
||||||
|
|
Loading…
Reference in New Issue