[Py-howto-checkins] CVS: pyhowto python-21.tex,1.4,1.5

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

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

Modified Files:
	python-21.tex 
Log Message:
Add introductory note about this article's draft status
Grammatical and typographic fixes from David Goodger
Expanded notes about PEP 229
Removed user-visible XXXes; they're in comments now


Index: python-21.tex
===================================================================
RCS file: /cvsroot/py-howto/pyhowto/python-21.tex,v
retrieving revision 1.4
retrieving revision 1.5
diff -C2 -r1.4 -r1.5
*** python-21.tex	2001/01/22 19:51:13	1.4
--- python-21.tex	2001/01/23 02:48:26	1.5
***************
*** 12,15 ****
--- 12,20 ----
  \section{Introduction}
  
+ {\large This document is a draft, and is subject to change until
+ Python 2.1 is released.  Please send any comments, bug reports, or questions,
+ no matter how minor, to \email{am...@bi...}.
+ }
+ 
  It's that time again... time for a new Python release, version 2.1.
  One recent goal of the Python development team has been to accelerate
***************
*** 45,49 ****
  SPARK parsing framework, docstrings hold parts of the BNF grammar to
  be parsed.  This overloading is unfortunate, since docstrings are
! really intended to hold a function's documentation, and means you
  can't properly document functions intended for private use in Zope.
  
--- 50,55 ----
  SPARK parsing framework, docstrings hold parts of the BNF grammar to
  be parsed.  This overloading is unfortunate, since docstrings are
! really intended to hold a function's documentation, and it 
! means you
  can't properly document functions intended for private use in Zope.
  
***************
*** 148,152 ****
  number of obsolete modules and features along the way.  It's difficult
  to know when a feature is safe to remove, since there's no way of
! knowing how much code uses it -- perhaps no programs depend on the
  feature, or perhaps many do.  To enable removing old features in a
  more structured way, a warning framework was added.  When the Python
--- 154,158 ----
  number of obsolete modules and features along the way.  It's difficult
  to know when a feature is safe to remove, since there's no way of
! knowing how much code uses it --- perhaps no programs depend on the
  feature, or perhaps many do.  To enable removing old features in a
  more structured way, a warning framework was added.  When the Python
***************
*** 224,229 ****
  installing extensions.  In Python 2.1, the Distutils are used to
  compile much of the standard library of extension modules,
! autodetecting which ones are supported on the current machine.  
! It's hoped that this will make Python installations easier and more featureful.
  
  \begin{seealso}
--- 230,253 ----
  installing extensions.  In Python 2.1, the Distutils are used to
  compile much of the standard library of extension modules,
! autodetecting which ones are supported on the current machine.  It's
! hoped that this will make Python installations easier and more
! featureful.
! 
! Instead of having to edit the \file{Modules/Setup} file in order to
! enable modules, a \file{setup.py} script in the top directory of the
! Python source distribution is run at build time, and attempts to
! discover which modules can be enabled by examining the modules and
! header files on the system.  In 2.1alpha1, there's very little you can
! do to change \file{setup.py}'s behaviour, or to discover why a given
! module isn't compiled.  If you run into problems in 2.1alpha1, please
! report them, and be prepared to dive into \file{setup.py} in order to
! fix autodetection of a given library on your system.  In the alpha2
! release I plan to add ways to have more control over what the script
! does (probably command-line arguments to \file{configure} or to
! \file{setup.py}).
! 
! If it turns out to be impossible to make autodetection work reliably,
! it's possible that this change may become an optional build method
! instead of the default, or it may even be backed out completely.
  
  \begin{seealso}
***************
*** 320,325 ****
  returns an opaque sequence object that only supports being iterated
  over, reading a line on every iteration but not reading the entire
! file into memory as the existing \method{readline()} method.  You'd
! use it like this:
  
  \begin{verbatim}
--- 344,349 ----
  returns an opaque sequence object that only supports being iterated
  over, reading a line on every iteration but not reading the entire
! file into memory as the existing \method{readlines()} method does.
! You'd use it like this:
  
  \begin{verbatim}
***************
*** 347,351 ****
  
  \item Modules can now control which names are imported when \code{from
! \var{module} import *} is used, by defining a \code{__all__} attribute
  containing a list of names that will be imported.  One common
  complaint is that if the module imports other modules such as
--- 371,375 ----
  
  \item Modules can now control which names are imported when \code{from
! \var{module} import *} is used, by defining an \code{__all__} attribute
  containing a list of names that will be imported.  One common
  complaint is that if the module imports other modules such as
***************
*** 403,414 ****
  
  % ======================================================================
! \section{XXX Nested Scopes ?}
  
- xxx
  
  % ======================================================================
! \section{XXX Weak References ?}
  
- xxx
  
  % ======================================================================
--- 427,457 ----
  
  % ======================================================================
! \section{Nested Scopes}
! 
! % XXX
! The PEP for this new feature hasn't been completed yet, and the
! requisite changes haven't been checked into CVS yet.
! 
! \begin{seealso}
! 
! \seepep{227}{Statically Nested Scopes}{Written and implemented by Jeremy Hylton.}
! 
! \end{seealso}
  
  
  % ======================================================================
! \section{Weak References}
! 
! % XXX
! The PEP for this new feature hasn't been completed yet, and the
! requisite changes haven't been checked into CVS yet.
! 
! 
! \begin{seealso}
! 
! \seepep{205}{Statically Nested Scopes}{Written and implemented by Jeremy Hylton.}
! 
! \end{seealso}
  
  
  % ======================================================================
***************
*** 416,422 ****
  
  The author would like to thank the following people for offering
! suggestions on various drafts of this article: Michael Hudson,
! Marc-Andr\'e Lemburg, 
! Neil Schemenauer, Thomas Wouters.
  
  \end{document}
--- 459,464 ----
  
  The author would like to thank the following people for offering
! suggestions on various drafts of this article: David Goodger, Michael
! Hudson, Marc-Andr\'e Lemburg, Neil Schemenauer, Thomas Wouters.
  
  \end{document}