2828window managers.
2929
3030Python is available for various operating systems, amongst which
31- several flavors of { \UNIX }, the Apple Macintosh, MS-DOS, Windows
31+ several flavors of \UNIX { }, the Apple Macintosh, MS-DOS, Windows
3232(3.1(1), '95 and NT flavors), OS/2, and others.
3333
3434This tutorial introduces the reader informally to the basic concepts
@@ -162,7 +162,7 @@ \section{Invoking the Interpreter}
162162
163163The Python interpreter is usually installed as {\tt /usr/local/bin/python}
164164on those machines where it is available; putting {\tt /usr/local/bin} in
165- your { \UNIX } shell's search path makes it possible to start it by
165+ your \UNIX { } shell's search path makes it possible to start it by
166166typing the command
167167
168168\bcode \begin {verbatim }
@@ -174,7 +174,7 @@ \section{Invoking the Interpreter}
174174your local Python guru or system administrator. (E.g., {\tt
175175/usr/local/python} is a popular alternative location.)
176176
177- The interpreter operates somewhat like the { \UNIX } shell: when called
177+ The interpreter operates somewhat like the \UNIX { } shell: when called
178178with standard input connected to a tty device, it reads and executes
179179commands interactively; when called with a file name argument or with
180180a file as standard input, it reads and executes a {\em script} from
@@ -223,7 +223,7 @@ \subsection{Interactive Mode}
223223>>>}); for continuation lines it prompts with the
224224{\em secondary\ prompt},
225225by default three dots ({\tt ...}). Typing an EOF character
226- (Control-D on { \UNIX }, Control-Z on DOS or Windows)
226+ (Control-D on \UNIX { }, Control-Z on DOS or Windows)
227227at the primary prompt causes the interpreter to exit with a zero exit
228228status.
229229
@@ -269,7 +269,7 @@ \subsection{The Module Search Path}
269269for a file named {\tt spam.py} in the current directory,
270270and then in the list of directories specified by
271271the environment variable {\tt PYTHONPATH}. This has the same syntax as
272- the { \UNIX } shell variable {\tt PATH}, i.e., a list of colon-separated
272+ the \UNIX { } shell variable {\tt PATH}, i.e., a list of colon-separated
273273directory names. When {\tt PYTHONPATH} is not set, or when the file
274274is not found there, the search continues in an installation-dependent
275275default path, usually {\tt .:/usr/local/lib/python}.
@@ -303,7 +303,7 @@ \subsection{``Compiled'' Python files}
303303
304304\subsection {Executable Python scripts }
305305
306- On BSD'ish { \UNIX } systems, Python scripts can be made directly
306+ On BSD'ish \UNIX { } systems, Python scripts can be made directly
307307executable, like shell scripts, by putting the line
308308
309309\bcode \begin {verbatim }
@@ -320,7 +320,7 @@ \subsection{The Interactive Startup File}
320320standard commands executed every time the interpreter is started. You
321321can do this by setting an environment variable named {\tt
322322PYTHONSTARTUP} to the name of a file containing your start-up
323- commands. This is similar to the {\tt .profile} feature of the UNIX
323+ commands. This is similar to the {\tt .profile} feature of the \ UNIX{}
324324shells.
325325
326326This file is only read in interactive sessions, not when Python reads
@@ -3229,9 +3229,9 @@ \section{New Class Features}
32293229
32303230\section {Unix Signal Handling }
32313231
3232- On { \UNIX }, Python now supports signal handling. The module
3232+ On \UNIX { }, Python now supports signal handling. The module
32333233\code {signal} exports functions \code {signal}, \code {pause} and
3234- \code {alarm}, which act similar to their { \UNIX } counterparts. The
3234+ \code {alarm}, which act similar to their \UNIX { } counterparts. The
32353235module also exports the conventional names for the various signal
32363236classes (also usable with \code {os.kill()}) and \code {SIG_IGN} and
32373237\code {SIG_DFL}. See the section on \code {signal} in the Library
0 commit comments