[Python-checkins] python/dist/src/Doc/tut tut.tex,1.184,1.185

fdrake@users.sourceforge.net fdrake@users.sourceforge.net
Tue, 20 May 2003 08:29:01 -0700


Update of /cvsroot/python/python/dist/src/Doc/tut
In directory sc8-pr-cvs1:/tmp/cvs-serv4922

Modified Files:
	tut.tex 
Log Message:
Markup nits.


Index: tut.tex
===================================================================
RCS file: /cvsroot/python/python/dist/src/Doc/tut/tut.tex,v
retrieving revision 1.184
retrieving revision 1.185
diff -C2 -d -r1.184 -r1.185
*** tut.tex	7 May 2003 17:49:36 -0000	1.184
--- tut.tex	20 May 2003 15:28:58 -0000	1.185
***************
*** 209,213 ****
  Note that there is a difference between \samp{python file} and
  \samp{python <file}.  In the latter case, input requests from the
! program, such as calls to \code{input()} and \code{raw_input()}, are
  satisfied from \emph{file}.  Since this file has already been read
  until the end by the parser before the program starts executing, the
--- 209,213 ----
  Note that there is a difference between \samp{python file} and
  \samp{python <file}.  In the latter case, input requests from the
! program, such as calls to \function{input()} and \function{raw_input()}, are
  satisfied from \emph{file}.  Since this file has already been read
  until the end by the parser before the program starts executing, the
***************
*** 272,277 ****
  the primary prompt; when input came from a file, it exits with a
  nonzero exit status after printing
! the stack trace.  (Exceptions handled by an \code{except} clause in a
! \code{try} statement are not errors in this context.)  Some errors are
  unconditionally fatal and cause an exit with a nonzero exit; this
  applies to internal inconsistencies and some cases of running out of
--- 272,277 ----
  the primary prompt; when input came from a file, it exits with a
  nonzero exit status after printing
! the stack trace.  (Exceptions handled by an \keyword{except} clause in a
! \keyword{try} statement are not errors in this context.)  Some errors are
  unconditionally fatal and cause an exit with a nonzero exit; this
  applies to internal inconsistencies and some cases of running out of
***************
*** 286,291 ****
  }
  Typing an interrupt while a command is executing raises the
! \code{KeyboardInterrupt} exception, which may be handled by a
! \code{try} statement.
  
  \subsection{Executable Python Scripts \label{scripts}}
--- 286,291 ----
  }
  Typing an interrupt while a command is executing raises the
! \exception{KeyboardInterrupt} exception, which may be handled by a
! \keyword{try} statement.
  
  \subsection{Executable Python Scripts \label{scripts}}