[Python-checkins] python/dist/src/Doc/ref ref3.tex,1.82.4.7,1.82.4.8

[fdrake@users.sourceforge.net]

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

Modified Files:
      Tag: release22-maint
	ref3.tex 
Log Message:
- backport portions of SF patch #700798: fixes and cleanups for descriptor info
- use a TeX "tie" to prevent word-wrapping in "section x.y"-like text


Index: ref3.tex
===================================================================
RCS file: /cvsroot/python/python/dist/src/Doc/ref/ref3.tex,v
retrieving revision 1.82.4.7
retrieving revision 1.82.4.8
diff -C2 -d -r1.82.4.7 -r1.82.4.8
*** ref3.tex	19 Jan 2003 14:54:08 -0000	1.82.4.7
--- ref3.tex	20 Mar 2003 18:22:50 -0000	1.82.4.8
***************
*** 389,393 ****
  
  Dictionaries are mutable; they can be created by the
! \code{\{...\}} notation (see section \ref{dict}, ``Dictionary
  Displays'').
  
--- 389,393 ----
  
  Dictionaries are mutable; they can be created by the
! \code{\{...\}} notation (see section~\ref{dict}, ``Dictionary
  Displays'').
  
***************
*** 400,404 ****
  \item[Callable types]
  These\obindex{callable} are the types to which the function call
! operation (see section \ref{calls}, ``Calls'') can be applied:
  \indexii{function}{call}
  \index{invocation}
--- 400,404 ----
  \item[Callable types]
  These\obindex{callable} are the types to which the function call
! operation (see section~\ref{calls}, ``Calls'') can be applied:
  \indexii{function}{call}
  \index{invocation}
***************
*** 409,413 ****
  \item[User-defined functions]
  A user-defined function object is created by a function definition
! (see section \ref{function}, ``Function definitions'').  It should be
  called with an argument
  list containing the same number of items as the function's formal
--- 409,413 ----
  \item[User-defined functions]
  A user-defined function object is created by a function definition
! (see section~\ref{function}, ``Function definitions'').  It should be
  called with an argument
  list containing the same number of items as the function's formal
***************
*** 577,582 ****
  
  \item[Modules]
! Modules are imported by the \keyword{import} statement (see section
! \ref{import}, ``The \keyword{import} statement'').
  A module object has a namespace implemented by a dictionary object
  (this is the dictionary referenced by the func_globals attribute of
--- 577,582 ----
  
  \item[Modules]
! Modules are imported by the \keyword{import} statement (see
! section~\ref{import}, ``The \keyword{import} statement'').
  A module object has a namespace implemented by a dictionary object
  (this is the dictionary referenced by the func_globals attribute of
***************
*** 613,618 ****
  
  \item[Classes]
! Class objects are created by class definitions (see section
! \ref{class}, ``Class definitions'').
  A class has a namespace implemented by a dictionary object.
  Class attribute references are translated to
--- 613,618 ----
  
  \item[Classes]
! Class objects are created by class definitions (see
! section~\ref{class}, ``Class definitions'').
  A class has a namespace implemented by a dictionary object.
  Class attribute references are translated to
***************
*** 684,688 ****
  Class instances can pretend to be numbers, sequences, or mappings if
  they have methods with certain special names.  See
! section \ref{specialnames}, ``Special method names.''
  \obindex{numeric}
  \obindex{sequence}
--- 684,688 ----
  Class instances can pretend to be numbers, sequences, or mappings if
  they have methods with certain special names.  See
! section~\ref{specialnames}, ``Special method names.''
  \obindex{numeric}
  \obindex{sequence}
***************
*** 834,838 ****
  traceback.  When an exception handler is entered, the stack trace is
  made available to the program.
! (See section \ref{try}, ``The \code{try} statement.'')
  It is accessible as \code{sys.exc_traceback}, and also as the third
  item of the tuple returned by \code{sys.exc_info()}.  The latter is
--- 834,838 ----
  traceback.  When an exception handler is entered, the stack trace is
  made available to the program.
! (See section~\ref{try}, ``The \code{try} statement.'')
  It is accessible as \code{sys.exc_traceback}, and also as the third
  item of the tuple returned by \code{sys.exc_info()}.  The latter is