[Python-checkins] python/dist/src/Doc/whatsnew whatsnew23.tex,1.151,1.152

akuchling@users.sourceforge.net akuchling@users.sourceforge.net
Wed, 16 Jul 2003 07:44:14 -0700


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

Modified Files:
	whatsnew23.tex 
Log Message:
Minor text changes; update bug/patch count (quite a jump!)

Index: whatsnew23.tex
===================================================================
RCS file: /cvsroot/python/python/dist/src/Doc/whatsnew/whatsnew23.tex,v
retrieving revision 1.151
retrieving revision 1.152
diff -C2 -d -r1.151 -r1.152
*** whatsnew23.tex	16 Jul 2003 04:00:14 -0000	1.151
--- whatsnew23.tex	16 Jul 2003 14:44:12 -0000	1.152
***************
*** 18,26 ****
  
  {\large This article is a draft, and is currently up to date for
! Python 2.3beta1.  Please send any additions, comments or errata to the
  author.}
  
  This article explains the new features in Python 2.3.  The tentative
! release date of Python 2.3 is currently scheduled for mid-2003.
  
  This article doesn't attempt to provide a complete specification of
--- 18,26 ----
  
  {\large This article is a draft, and is currently up to date for
! Python 2.3rc1.  Please send any additions, comments or errata to the
  author.}
  
  This article explains the new features in Python 2.3.  The tentative
! release date of Python 2.3 is currently scheduled for August 2003.
  
  This article doesn't attempt to provide a complete specification of
***************
*** 29,34 ****
  such as the \citetitle[../lib/lib.html]{Python Library Reference} and
  the \citetitle[../ref/ref.html]{Python Reference Manual}.  If you want
! to understand the complete implementation and design rationale for a
! change, refer to the PEP for a particular new feature.
  
  
--- 29,34 ----
  such as the \citetitle[../lib/lib.html]{Python Library Reference} and
  the \citetitle[../ref/ref.html]{Python Reference Manual}.  If you want
! to understand the complete implementation and design rationale, 
! refer to the PEP for a particular new feature.
  
  
***************
*** 62,67 ****
  
  The union and intersection of sets can be computed with the
! \method{union()} and \method{intersection()} methods or
! alternatively using the bitwise operators \code{\&} and \code{|}.
  Mutable sets also have in-place versions of these methods,
  \method{union_update()} and \method{intersection_update()}.
--- 62,67 ----
  
  The union and intersection of sets can be computed with the
! \method{union()} and \method{intersection()} methods; an alternative
! notation uses the bitwise operators \code{\&} and \code{|}.
  Mutable sets also have in-place versions of these methods,
  \method{union_update()} and \method{intersection_update()}.
***************
*** 86,91 ****
  It's also possible to take the symmetric difference of two sets.  This
  is the set of all elements in the union that aren't in the
! intersection.  An alternative way of expressing the symmetric
! difference is that it contains all elements that are in exactly one
  set.  Again, there's an alternative notation (\code{\^}), and an
  in-place version with the ungainly name
--- 86,91 ----
  It's also possible to take the symmetric difference of two sets.  This
  is the set of all elements in the union that aren't in the
! intersection.  Another way of putting it is that the symmetric
! difference contains all elements that are in exactly one
  set.  Again, there's an alternative notation (\code{\^}), and an
  in-place version with the ungainly name
***************
*** 287,292 ****
  
  Without such an encoding declaration, the default encoding used is
! 7-bit ASCII.  Executing or importing modules containing string
! literals with 8-bit characters and no encoding declaration will result
  in a \exception{DeprecationWarning} being signalled by Python 2.3; in
  2.4 this will be a syntax error.
--- 287,292 ----
  
  Without such an encoding declaration, the default encoding used is
! 7-bit ASCII.  Executing or importing modules that contain string
! literals with 8-bit characters and have no encoding declaration will result
  in a \exception{DeprecationWarning} being signalled by Python 2.3; in
  2.4 this will be a syntax error.
***************
*** 347,354 ****
  The three major operating systems used today are Microsoft Windows,
  Apple's Macintosh OS, and the various \UNIX\ derivatives.  A minor
! irritation is that these three platforms all use different characters
  to mark the ends of lines in text files.  \UNIX\ uses the linefeed
! (ASCII character 10), while MacOS uses the carriage return (ASCII
! character 13), and Windows uses a two-character sequence containing a
  carriage return plus a newline.
  
--- 347,355 ----
  The three major operating systems used today are Microsoft Windows,
  Apple's Macintosh OS, and the various \UNIX\ derivatives.  A minor
! irritation of cross-platform work 
! is that these three platforms all use different characters
  to mark the ends of lines in text files.  \UNIX\ uses the linefeed
! (ASCII character 10), MacOS uses the carriage return (ASCII
! character 13), and Windows uses a two-character sequence of a
  carriage return plus a newline.
  
***************
*** 366,371 ****
  without needing to convert the line-endings.
  
! This feature can be disabled at compile-time by specifying
! \longprogramopt{without-universal-newlines} when running Python's
  \program{configure} script.
  
--- 367,372 ----
  without needing to convert the line-endings.
  
! This feature can be disabled when compiling Python by specifying
! the \longprogramopt{without-universal-newlines} switch when running Python's
  \program{configure} script.
  
***************
*** 387,392 ****
  \var{thing}[1])}, \code{(2, \var{thing}[2])}, and so forth.  
  
! Fairly often you'll see code to change every element of a list that
! looks like this:
  
  \begin{verbatim}
--- 388,392 ----
  \var{thing}[1])}, \code{(2, \var{thing}[2])}, and so forth.  
  
! A common idiom to change every element of a list looks like this:
  
  \begin{verbatim}
***************
*** 2213,2217 ****
  As usual, there were a bunch of other improvements and bugfixes
  scattered throughout the source tree.  A search through the CVS change
! logs finds there were 121 patches applied and 103 bugs fixed between
  Python 2.2 and 2.3.  Both figures are likely to be underestimates.
  
--- 2213,2217 ----
  As usual, there were a bunch of other improvements and bugfixes
  scattered throughout the source tree.  A search through the CVS change
! logs finds there were 523 patches applied and 514 bugs fixed between
  Python 2.2 and 2.3.  Both figures are likely to be underestimates.