[Python-checkins] python/dist/src/Doc/whatsnew whatsnew23.tex,1.77,1.78

[akuchling@users.sourceforge.net]

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

Modified Files:
	whatsnew23.tex 
Log Message:
Mention dict.fromkeys()
Various edits


Index: whatsnew23.tex
===================================================================
RCS file: /cvsroot/python/python/dist/src/Doc/whatsnew/whatsnew23.tex,v
retrieving revision 1.77
retrieving revision 1.78
diff -C2 -d -r1.77 -r1.78
*** whatsnew23.tex	26 Nov 2002 22:07:35 -0000	1.77
--- whatsnew23.tex	27 Nov 2002 19:11:10 -0000	1.78
***************
*** 616,624 ****
  \exception{UnicodeError}), ``ignore'' (skip the character), or
  ``replace'' (with question mark), defaulting to ``strict''. It may be
! desirable to specify an alternative processing of the error, e.g. by
  inserting an XML character reference or HTML entity reference into the
  converted string.
  
! Python now has a flexible framework to add additional processing
  strategies.  New error handlers can be added with
  \function{codecs.register_error}. Codecs then can access the error
--- 616,624 ----
  \exception{UnicodeError}), ``ignore'' (skip the character), or
  ``replace'' (with question mark), defaulting to ``strict''. It may be
! desirable to specify an alternative processing of the error, such as 
  inserting an XML character reference or HTML entity reference into the
  converted string.
  
! Python now has a flexible framework to add different processing
  strategies.  New error handlers can be added with
  \function{codecs.register_error}. Codecs then can access the error
***************
*** 632,636 ****
  Two additional error handlers have been implemented using this
  framework: ``backslashreplace'' uses Python backslash quoting to
! represent the unencodable character, and ``xmlcharrefreplace'' emits
  XML character references.
  
--- 632,636 ----
  Two additional error handlers have been implemented using this
  framework: ``backslashreplace'' uses Python backslash quoting to
! represent unencodable characters and ``xmlcharrefreplace'' emits
  XML character references.
  
***************
*** 822,826 ****
  \end{verbatim}
  
! (Patch contributed by Raymond Hettinger.)
  
  \item The \keyword{assert} statement no longer checks the \code{__debug__}
--- 822,832 ----
  \end{verbatim}
  
! There's also a new class method, 
! \method{dict.fromkeys(\var{iterable}, \var{value})}, that 
! creates a dictionary with keys taken from the supplied iterator
! \var{iterable} and all values set to \var{value}, defaulting to
! \code{None}.  
! 
! (Patches contributed by Raymond Hettinger.)
  
  \item The \keyword{assert} statement no longer checks the \code{__debug__}
***************
*** 1284,1301 ****
  per-use basis.
  
! \item Calling Tcl methods through \module{_tkinter} now does not
! always return strings anymore. Instead, if Tcl returns other objects,
! those objects are converted to their Python equivalent, if one exists,
! or wrapped with a \class{_tkinter.Tcl_Obj} object if no Python
! equivalent exists. This behaviour can be controlled through the
! \method{wantobjects} method of \class{tkapp} objects.
  
! When using _tkinter through Tkinter.py (i.e. for most _tkinter
! applications), this feature is always activated. It should not cause
! compatibility problems, since Tkinter would always convert string
! results to Python types were possible.
  
  If any incompatibilities are found, the old behaviour can be restored
! by invoking
  
  \begin{verbatim}
--- 1290,1308 ----
  per-use basis.
  
! \item Calling Tcl methods through \module{_tkinter} no longer 
! returns only strings. Instead, if Tcl returns other objects those
! objects are converted to their Python equivalent, if one exists, or
! wrapped with a \class{_tkinter.Tcl_Obj} object if no Python equivalent
! exists. This behaviour can be controlled through the
! \method{wantobjects()} method of \class{tkapp} objects.
  
! When using \module{_tkinter} through the \module{Tkinter} module (as
! most Tkinter applications will), this feature is always activated. It
! should not cause compatibility problems, since Tkinter would always
! convert string results to Python types where possible.
  
  If any incompatibilities are found, the old behaviour can be restored
! by setting the \member{wantobjects} variable in the \module{Tkinter}
! module to false before creating the first \class{tkapp} object.
  
  \begin{verbatim}
***************
*** 1304,1310 ****
  \end{verbatim}
  
! before creating the first \class{tkapp} object.
! 
! Please report any such breakage as a bug.
  
  \end{itemize}
--- 1311,1315 ----
  \end{verbatim}
  
! Please report any breakage caused by this change as a bug.
  
  \end{itemize}
***************
*** 1652,1655 ****
--- 1657,1666 ----
  integer instead of raising an \exception{OverflowError} when a string
  or floating-point number is too large to fit into an integer.
+ 
+ \item Calling Tcl methods through \module{_tkinter} no longer 
+ returns only strings. Instead, if Tcl returns other objects those
+ objects are converted to their Python equivalent, if one exists, or
+ wrapped with a \class{_tkinter.Tcl_Obj} object if no Python equivalent
+ exists.
  
  \item You can no longer disable assertions by assigning to \code{__debug__}.