[Python-checkins] CVS: python/dist/src/Doc/lib libcodeop.tex,1.4,1.5

2001年8月28日 07:25:05 -0700

Update of /cvsroot/python/python/dist/src/Doc/lib
In directory usw-pr-cvs1:/tmp/cvs-serv6852/lib
Modified Files:
	libcodeop.tex 
Log Message:
Fix a number of minor markup errors, and improve the consistency a bit.
Index: libcodeop.tex
===================================================================
RCS file: /cvsroot/python/python/dist/src/Doc/lib/libcodeop.tex,v
retrieving revision 1.4
retrieving revision 1.5
diff -C2 -d -r1.4 -r1.5
*** libcodeop.tex	2001年08月27日 20:02:16	1.4
--- libcodeop.tex	2001年08月28日 14:25:03	1.5
***************
*** 10,27 ****

 The \module{codeop} module provides utilities upon which the Python
! read-eval-print loop can be emulated -- as in the \refmodule{code}
! module. As a result, you probably don't want to use the module
! directly -- if you want to include such a loop in your program you
! probably want to use the \refmodule{code} instead.

 There are two parts to this job: 

! \begin{list}
! \listitem Being able to tell if a line of input completes a Python 
! statement -- in short telling whether to print ``>>> '' or
! ``... '' next.
! \listitem Remembering which future statements the user has entered, so 
! subsequent input can be compiled wiht these in effect.
! \end{list}

 The \module{codeop} module provides a way of doing each of these
--- 10,27 ----

 The \module{codeop} module provides utilities upon which the Python
! read-eval-print loop can be emulated, as is done in the
! \refmodule{code} module. As a result, you probably don't want to use
! the module directly; if you want to include such a loop in your
! program you probably want to use the \refmodule{code} module instead.

 There are two parts to this job: 

! \begin{enumerate}
! \item Being able to tell if a line of input completes a Python 
! statement: in short, telling whether to print
! `\code{>\code{>}>~} or `\code{...~}' next.
! \item Remembering which future statements the user has entered, so 
! subsequent input can be compiled with these in effect.
! \end{enumerate}

 The \module{codeop} module provides a way of doing each of these
***************
*** 59,64 ****

 \begin{classdesc}{Compile}{}
! Instances of this class have \method{__call__} methods indentical in
! signature to the built-in function \function{compile}, but with the
 difference that if the instance compiles program text containing a
 \module{__future__} statement, the instance 'remembers' and compiles
--- 59,64 ----

 \begin{classdesc}{Compile}{}
! Instances of this class have \method{__call__()} methods indentical in
! signature to the built-in function \function{compile()}, but with the
 difference that if the instance compiles program text containing a
 \module{__future__} statement, the instance 'remembers' and compiles
***************
*** 67,73 ****

 \begin{classdesc}{CommandCompiler}{}
! Instances of this class have \method{__call__} methods identical in
! signature to \function{compile_command}; the difference is that if the
! instance compiles program text containing a \method{__future__}
 statement, the instance 'remembers' and compiles all subsequent
 program texts with the statement in force.
--- 67,73 ----

 \begin{classdesc}{CommandCompiler}{}
! Instances of this class have \method{__call__()} methods identical in
! signature to \function{compile_command()}; the difference is that if
! the instance compiles program text containing a \code{__future__}
 statement, the instance 'remembers' and compiles all subsequent
 program texts with the statement in force.