[Python-checkins] python/dist/src/Doc/lib libfuture.tex,1.2,1.3

[fdrake at users.sourceforge.net]

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

Modified Files:
	libfuture.tex 
Log Message:
markup updates


Index: libfuture.tex
===================================================================
RCS file: /cvsroot/python/python/dist/src/Doc/lib/libfuture.tex,v
retrieving revision 1.2
retrieving revision 1.3
diff -C2 -d -r1.2 -r1.3
*** libfuture.tex	5 Aug 2003 11:40:21 -0000	1.2
--- libfuture.tex	5 Sep 2003 15:50:20 -0000	1.3
***************
*** 26,36 ****
  Each statement in \file{__future__.py} is of the form:
  
! \begin{verbatim}
! FeatureName = "_Feature(" OptionalRelease "," MandatoryRelease ","
!                         CompilerFlag ")"
! \end{verbatim}
  
! where, normally, OptionalRelease is less then MandatoryRelease, and
! both are 5-tuples of the same form as \code{sys.version_info}:
  
  \begin{verbatim}
--- 26,37 ----
  Each statement in \file{__future__.py} is of the form:
  
! \begin{alltt}
! FeatureName = "_Feature(" \var{OptionalRelease} "," \var{MandatoryRelease} ","
!                         \var{CompilerFlag} ")"
! \end{alltt}
  
! where, normally, \var{OptionalRelease} is less than
! \var{MandatoryRelease}, and both are 5-tuples of the same form as
! \code{sys.version_info}:
  
  \begin{verbatim}
***************
*** 43,59 ****
  \end{verbatim}
  
! OptionalRelease records the first release in which the feature was
! accepted. 
  
! In the case of MandatoryReleases that have not yet occurred,
! MandatoryRelease predicts the release in which the feature will become
! part of the language.
  
! Else MandatoryRelease records when the feature became part of the
! language; in releases at or after that, modules no longer need a
  future statement to use the feature in question, but may continue to
! use such imports. 
  
! MandatoryRelease may also be \code{None}, meaning that a planned
  feature got dropped.
  
--- 44,60 ----
  \end{verbatim}
  
! \var{OptionalRelease} records the first release in which the feature
! was accepted.
  
! In the case of a \var{MandatoryRelease} that has not yet occurred,
! \var{MandatoryRelease} predicts the release in which the feature will
! become part of the language.
  
! Else \var{MandatoryRelease} records when the feature became part of
! the language; in releases at or after that, modules no longer need a
  future statement to use the feature in question, but may continue to
! use such imports.
  
! \var{MandatoryRelease} may also be \code{None}, meaning that a planned
  feature got dropped.
  
***************
*** 61,65 ****
  \method{getOptionalRelease()} and \method{getMandatoryRelease()}.
  
! CompilerFlag is the (bitfield) flag that should be passed in the
  fourth argument to the builtin function \function{compile()} to enable
  the feature in dynamically compiled code.  This flag is stored in the
--- 62,66 ----
  \method{getOptionalRelease()} and \method{getMandatoryRelease()}.
  
! \var{CompilerFlag} is the (bitfield) flag that should be passed in the
  fourth argument to the builtin function \function{compile()} to enable
  the feature in dynamically compiled code.  This flag is stored in the
***************
*** 67,69 ****
  
  No feature description will ever be deleted from \module{__future__}.
- 
--- 68,69 ----