py-howto-checkins

[A.M. K. <aku...@us...>]

Update of /cvsroot/py-howto/pyhowto
In directory usw-pr-cvs1:/tmp/cvs-serv30850

Modified Files:
	python-22.tex 
Log Message:
Fill in remaining XXX spots
        - Describe UnpackTuple()
        - Credit __unicode__ to MAL
Use \pep macro everywhere in body text.
   (Listening to "The Great Gate of Kiev" -- appropriately triumphal
    music for this check-in...)


Index: python-22.tex
===================================================================
RCS file: /cvsroot/py-howto/pyhowto/python-22.tex,v
retrieving revision 1.37
retrieving revision 1.38
diff -C2 -r1.37 -r1.38
*** python-22.tex	2001/10/26 20:07:03	1.37
--- python-22.tex	2001/10/26 20:37:55	1.38
***************
*** 115,119 ****
  I'm not going to attempt to cover every single corner case and small
  change that were required to make the new features work.  Instead this
! section will paint only the broad strokes.  See section~\cite{sect-rellinks},
  ``Related Links'', for further sources of information about Python 2.2's new
  object model.
--- 115,119 ----
  I'm not going to attempt to cover every single corner case and small
  change that were required to make the new features work.  Instead this
! section will paint only the broad strokes.  See section~\ref{sect-rellinks},
  ``Related Links'', for further sources of information about Python 2.2's new
  object model.
***************
*** 145,152 ****
  
  This means that \keyword{class} statements that don't have any base
! classes are always classic classes in Python 2.2.  There's actually a
! way to make new-style classes without any base classes, by setting the
! \member{__metaclass__} variable to XXX (What do you set it to?), but
! it's easier to just subclass \keyword{object}.
  
  The type objects for the built-in types are available as built-ins,
--- 145,152 ----
  
  This means that \keyword{class} statements that don't have any base
! classes are always classic classes in Python 2.2.  (Actually you can
! also change this by setting a module-level variable named
! \member{__metaclass__} --- see \pep{253} for the details --- but it's
! easier to just subclass \keyword{object}.)
  
  The type objects for the built-in types are available as built-ins,
***************
*** 430,434 ****
  
  \subsection{Related Links}
! \ref{sect-rellinks}
  
  This section has just been a quick overview of the new features,
--- 430,434 ----
  
  \subsection{Related Links}
! \label{sect-rellinks}
  
  This section has just been a quick overview of the new features,
***************
*** 640,644 ****
  \keyword{yield} statement.  (For complicated reasons, the
  \keyword{yield} statement isn't allowed inside the \keyword{try} block
! of a \code{try...finally} statement; read PEP 255 for a full
  explanation of the interaction between \keyword{yield} and
  exceptions.)
--- 640,644 ----
  \keyword{yield} statement.  (For complicated reasons, the
  \keyword{yield} statement isn't allowed inside the \keyword{try} block
! of a \code{try...finally} statement; read \pep{255} for a full
  explanation of the interaction between \keyword{yield} and
  exceptions.)
***************
*** 804,808 ****
  storm of acidly sarcastic postings on \newsgroup{comp.lang.python}. I
  won't argue for either side here and will stick to describing what's 
! implemented in 2.2.  Read PEP 238 for a summary of arguments and
  counter-arguments.)  
  
--- 804,808 ----
  storm of acidly sarcastic postings on \newsgroup{comp.lang.python}. I
  won't argue for either side here and will stick to describing what's 
! implemented in 2.2.  Read \pep{238} for a summary of arguments and
  counter-arguments.)  
  
***************
*** 811,815 ****
  complete until Python 3.0.
  
! First, I'll borrow some terminology from PEP 238.  ``True division'' is the
  division that most non-programmers are familiar with: 3/2 is 1.5, 1/4
  is 0.25, and so forth.  ``Floor division'' is what Python's \code{/}
--- 811,815 ----
  complete until Python 3.0.
  
! First, I'll borrow some terminology from \pep{238}.  ``True division'' is the
  division that most non-programmers are familiar with: 3/2 is 1.5, 1/4
  is 0.25, and so forth.  ``Floor division'' is what Python's \code{/}
***************
*** 844,848 ****
  so extension types can define the two operators.
  
! % XXX a warning someday?
  
  \end{itemize}
--- 844,854 ----
  so extension types can define the two operators.
  
! \item Python 2.2 supports some command-line arguments for testing
! whether code will works with the changed division semantics.  Running
! python with \programopt{-Q warn} will cause a warning to be issued
! whenever division is applied to two integers.  You can use this to
! find code that's affected by the change and fix it.  By default,
! Python 2.2 will simply perform classic division without a warning; the
! warning will be turned on by default in Python 2.3.
  
  \end{itemize}
***************
*** 872,876 ****
  
  % XXX is this still unimplemented?
! All this is the province of the still-unimplemented PEP 261, ``Support
  for `wide' Unicode characters''; consult it for further details, and
  please offer comments on the PEP and on your experiences with the
--- 878,882 ----
  
  % XXX is this still unimplemented?
! All this is the province of the still-unimplemented \pep{261}, ``Support
  for `wide' Unicode characters''; consult it for further details, and
  please offer comments on the PEP and on your experiences with the
***************
*** 911,920 ****
  
  To convert a class instance to Unicode, a \method{__unicode__} method
! can be defined, analogous to \method{__str__}.
! % XXX who implemented that?
  
! \method{encode()} and \method{decode()} were implemented by
! Marc-Andr\'e Lemburg.  The changes to support using UCS-4 internally
! were implemented by Fredrik Lundh and Martin von L\"owis.
  
  \begin{seealso}
--- 917,926 ----
  
  To convert a class instance to Unicode, a \method{__unicode__} method
! can be defined by a class, analogous to \method{__str__}.
  
! \method{encode()}, \method{decode()}, and \method{__unicode__} were
! implemented by Marc-Andr\'e Lemburg.  The changes to support using
! UCS-4 internally were implemented by Fredrik Lundh and Martin von
! L\"owis.
  
  \begin{seealso}
***************
*** 925,928 ****
--- 931,935 ----
  \end{seealso}
  
+ 
  %======================================================================
  \section{PEP 227: Nested Scopes}
***************
*** 1147,1152 ****
  affect you very much.
  
- % XXX PyArg_UnpackTuple()
- 
  \begin{itemize}
  
--- 1154,1157 ----
***************
*** 1181,1185 ****
    (Contributed by M.-A. Lemburg, and used for the MBCS support on
    Windows described in the following section.)
!  
    \item Two new flags \constant{METH_NOARGS} and \constant{METH_O} are
     available in method definition tables to simplify implementation of
--- 1186,1197 ----
    (Contributed by M.-A. Lemburg, and used for the MBCS support on
    Windows described in the following section.)
! 
!   \item A different argument parsing function,
!   \cfunction{PyArg_UnpackTuple()}, has been added that's simpler and
!   presumably faster.  Instead of specifying a format string, the
!   caller simply gives the minimum and maximum number of arguments
!   expected, and a set of pointers to \code{PyObject*} variables that
!   will be filled in with argument values.  
! 
    \item Two new flags \constant{METH_NOARGS} and \constant{METH_O} are
     available in method definition tables to simplify implementation of