[Python-checkins] python/dist/src/Doc/whatsnew whatsnew23.tex,1.156,1.157

akuchling@users.sourceforge.net akuchling@users.sourceforge.net
Thu, 17 Jul 2003 19:12:18 -0700


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

Modified Files:
	whatsnew23.tex 
Log Message:
Add introductory paragraphs
Remove comment about MacOS changes; I'm not going to have time to figure 
    out what they are
Move PEP 273 section into numeric order


Index: whatsnew23.tex
===================================================================
RCS file: /cvsroot/python/python/dist/src/Doc/whatsnew/whatsnew23.tex,v
retrieving revision 1.156
retrieving revision 1.157
diff -C2 -d -r1.156 -r1.157
*** whatsnew23.tex	18 Jul 2003 01:15:51 -0000	1.156
--- whatsnew23.tex	18 Jul 2003 02:12:16 -0000	1.157
***************
*** 12,22 ****
  \tableofcontents
  
! % To do:
! % MacOS framework-related changes (section of its own, probably)
  
! %\section{Introduction \label{intro}}
  
! 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
--- 12,34 ----
  \tableofcontents
  
! This article explains the new features in Python 2.3.  The 
! release date of Python 2.3 is currently scheduled for August 2003.
  
! The main themes for Python 2.3 are polishing some of the features
! added in 2.2, adding various small but useful enhancements to the core
! language, and expanding the standard library.  The new object model
! introduced in the previous version has benefited from 18 months of
! bugfixes and from optimization efforts that have improved the
! performance of new-style classes.  A few new built-in functions have
! been added such as \function{sum()} and \function{enumerate()}.  The
! \keyword{in} operator can now be used for substring searches (e.g.
! \code{"ab" in "abc"} returns \constant{True}).
  
! Some of the many new library features include Boolean, set, heap, and
! date/time data types, the ability to import modules from ZIP-format
! archives, metadata support for the long-awaited Python catalog, an
! updated version of IDLE, and modules for logging messages, wrapping
! text, parsing CSV files, processing command-line options, using BerkeleyDB
! databases...  the list of new and enhanced modules is lengthy.
  
  This article doesn't attempt to provide a complete specification of
***************
*** 304,307 ****
--- 316,370 ----
  
  %======================================================================
+ \section{PEP 273: Importing Modules from Zip Archives}
+ 
+ The new \module{zipimport} module adds support for importing
+ modules from a ZIP-format archive.  You don't need to import the
+ module explicitly; it will be automatically imported if a ZIP
+ archive's filename is added to \code{sys.path}.  For example:
+ 
+ \begin{verbatim}
+ amk@nyman:~/src/python$ unzip -l /tmp/example.zip
+ Archive:  /tmp/example.zip
+   Length     Date   Time    Name
+  --------    ----   ----    ----
+      8467  11-26-02 22:30   jwzthreading.py
+  --------                   -------
+      8467                   1 file
+ amk@nyman:~/src/python$ ./python
+ Python 2.3 (#1, Aug 1 2003, 19:54:32) 
+ >>> import sys
+ >>> sys.path.insert(0, '/tmp/example.zip')  # Add .zip file to front of path
+ >>> import jwzthreading
+ >>> jwzthreading.__file__
+ '/tmp/example.zip/jwzthreading.py'
+ >>>
+ \end{verbatim}
+ 
+ An entry in \code{sys.path} can now be the filename of a ZIP archive.
+ The ZIP archive can contain any kind of files, but only files named
+ \file{*.py}, \file{*.pyc}, or \file{*.pyo} can be imported.  If an
+ archive only contains \file{*.py} files, Python will not attempt to
+ modify the archive by adding the corresponding \file{*.pyc} file, meaning
+ that if a ZIP archive doesn't contain \file{*.pyc} files, importing may be
+ rather slow.
+ 
+ A path within the archive can also be specified to only import from a
+ subdirectory; for example, the path \file{/tmp/example.zip/lib/}
+ would only import from the \file{lib/} subdirectory within the
+ archive.
+ 
+ \begin{seealso}
+ 
+ \seepep{273}{Import Modules from Zip Archives}{Written by James C. Ahlstrom, 
+ who also provided an implementation.
+ Python 2.3 follows the specification in \pep{273}, 
+ but uses an implementation written by Just van~Rossum 
+ that uses the import hooks described in \pep{302}.
+ See section~\ref{section-pep302} for a description of the new import hooks.
+ }
+ 
+ \end{seealso}
+ 
+ %======================================================================
  \section{PEP 277: Unicode file name support for Windows NT}
  
***************
*** 653,707 ****
  \end{seealso}
  
- 
- %======================================================================
- \section{PEP 273: Importing Modules from Zip Archives}
- 
- The new \module{zipimport} module adds support for importing
- modules from a ZIP-format archive.  You don't need to import the
- module explicitly; it will be automatically imported if a ZIP
- archive's filename is added to \code{sys.path}.  For example:
- 
- \begin{verbatim}
- amk@nyman:~/src/python$ unzip -l /tmp/example.zip
- Archive:  /tmp/example.zip
-   Length     Date   Time    Name
-  --------    ----   ----    ----
-      8467  11-26-02 22:30   jwzthreading.py
-  --------                   -------
-      8467                   1 file
- amk@nyman:~/src/python$ ./python
- Python 2.3 (#1, Aug 1 2003, 19:54:32) 
- >>> import sys
- >>> sys.path.insert(0, '/tmp/example.zip')  # Add .zip file to front of path
- >>> import jwzthreading
- >>> jwzthreading.__file__
- '/tmp/example.zip/jwzthreading.py'
- >>>
- \end{verbatim}
- 
- An entry in \code{sys.path} can now be the filename of a ZIP archive.
- The ZIP archive can contain any kind of files, but only files named
- \file{*.py}, \file{*.pyc}, or \file{*.pyo} can be imported.  If an
- archive only contains \file{*.py} files, Python will not attempt to
- modify the archive by adding the corresponding \file{*.pyc} file, meaning
- that if a ZIP archive doesn't contain \file{*.pyc} files, importing may be
- rather slow.
- 
- A path within the archive can also be specified to only import from a
- subdirectory; for example, the path \file{/tmp/example.zip/lib/}
- would only import from the \file{lib/} subdirectory within the
- archive.
- 
- \begin{seealso}
- 
- \seepep{273}{Import Modules from Zip Archives}{Written by James C. Ahlstrom, 
- who also provided an implementation.
- Python 2.3 follows the specification in \pep{273}, 
- but uses an implementation written by Just van~Rossum 
- that uses the import hooks described in \pep{302}.
- See section~\ref{section-pep302} for a description of the new import hooks.
- }
- 
- \end{seealso}
  
  %======================================================================
--- 716,719 ----