Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Commit b2d1006

Browse files
committed
Update the description of how to start an interpreter and determine the
installation prefix and exec_prefix for Windows.
1 parent b4b64da commit b2d1006

1 file changed

Lines changed: 6 additions & 5 deletions

File tree

Doc/inst/inst.tex

Lines changed: 6 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -361,12 +361,13 @@ \subsection{How installation works}
361361
often the same under \UNIX. You can find out what your Python
362362
installation uses for \filevar{prefix} and \filevar{exec-prefix} by
363363
running Python in interactive mode and typing a few simple commands.
364-
Under \UNIX, just type \code{python} at the shell prompt; under Windows,
365-
run ``Python 2.0 (interpreter)'' \XXX{right?}; under MacOS, \XXX{???}.
364+
Under \UNIX, just type \code{python} at the shell prompt. Under
365+
Windows, choose \menuselection{Start \sub Programs \sub Python
366+
2.1 \sub Python (command line)}. Under MacOS, \XXX{???}.
366367
Once the interpreter is started, you type Python code at the
367-
\samp{>\code{>}> } prompt. For example, on my Linux system, I type the three
368-
Python statements shown below, and get the output as shown, to find
369-
out my \filevar{prefix} and \filevar{exec-prefix}:
368+
prompt. For example, on my Linux system, I type the three Python
369+
statements shown below, and get the output as shown, to find out my
370+
\filevar{prefix} and \filevar{exec-prefix}:
370371

371372
\begin{verbatim}
372373
Python 1.5.2 (#1, Apr 18 1999, 16:03:16) [GCC pgcc-2.91.60 19981201 (egcs-1.1.1 on linux2

0 commit comments

Comments
 (0)