Fri, 13 Jul 2001 19:50:57 -0700

Update of /cvsroot/python/python/dist/src/Doc/lib
In directory usw-pr-cvs1:/tmp/cvs-serv22682

Modified Files:
	internet.tex lib.tex libasyncore.tex libbase64.tex 
	libbasehttp.tex libcgi.tex libfl.tex libformatter.tex 
	libintro.tex libos.tex libpanel.tex libresource.tex 
	librestricted.tex librexec.tex librobotparser.tex 
	libstdwin.tex libtime.tex libunittest.tex liburllib.tex 
	liburlparse.tex libxmllib.tex 
Log Message:

Minor changes to match the style guide.

Index: internet.tex
===================================================================
RCS file: /cvsroot/python/python/dist/src/Doc/lib/internet.tex,v
retrieving revision 1.3
retrieving revision 1.4
diff -C2 -r1.3 -r1.4
*** internet.tex	2000/04/03 20:13:52	1.3
--- internet.tex	2001/07/14 02:50:55	1.4
***************
*** 3,7 ****
  \index{WWW}
  \index{Internet}
! \index{World-Wide Web}

  The modules described in this chapter implement Internet protocols and 
--- 3,7 ----
  \index{WWW}
  \index{Internet}
! \index{World Wide Web}

  The modules described in this chapter implement Internet protocols and 

Index: lib.tex
===================================================================
RCS file: /cvsroot/python/python/dist/src/Doc/lib/lib.tex,v
retrieving revision 1.188
retrieving revision 1.189
diff -C2 -r1.188 -r1.189
*** lib.tex	2001/07/12 23:40:13	1.188
--- lib.tex	2001/07/14 02:50:55	1.189
***************
*** 29,33 ****
  Python is an extensible, interpreted, object-oriented programming
  language.  It supports a wide range of applications, from simple text
! processing scripts to interactive WWW browsers.

  While the \citetitle[../ref/ref.html]{Python Reference Manual}
--- 29,33 ----
  Python is an extensible, interpreted, object-oriented programming
  language.  It supports a wide range of applications, from simple text
! processing scripts to interactive Web browsers.

  While the \citetitle[../ref/ref.html]{Python Reference Manual}

Index: libasyncore.tex
===================================================================
RCS file: /cvsroot/python/python/dist/src/Doc/lib/libasyncore.tex,v
retrieving revision 1.8
retrieving revision 1.9
diff -C2 -r1.8 -r1.9
*** libasyncore.tex	2001/05/29 15:37:45	1.8
--- libasyncore.tex	2001/07/14 02:50:55	1.9
***************
*** 18,23 ****
  multi-threading, without actually using multiple threads.  It's really 
  only practical if your program is largely I/O bound.  If your program 
! is CPU bound, then pre-emptive scheduled threads are probably what 
! you really need. Network servers are rarely CPU-bound, however.

  If your operating system supports the \cfunction{select()} system call 
--- 18,23 ----
  multi-threading, without actually using multiple threads.  It's really 
  only practical if your program is largely I/O bound.  If your program 
! is processor bound, then pre-emptive scheduled threads are probably what 
! you really need. Network servers are rarely processor bound, however.

  If your operating system supports the \cfunction{select()} system call 

Index: libbase64.tex
===================================================================
RCS file: /cvsroot/python/python/dist/src/Doc/lib/libbase64.tex,v
retrieving revision 1.17
retrieving revision 1.18
diff -C2 -r1.17 -r1.18
*** libbase64.tex	2001/04/12 16:47:17	1.17
--- libbase64.tex	2001/07/14 02:50:55	1.18
***************
*** 10,14 ****

  This module performs base64 encoding and decoding of arbitrary binary
! strings into text strings that can be safely emailed or posted.  The
  encoding scheme is defined in \rfc{1521} (\emph{MIME
  (Multipurpose Internet Mail Extensions) Part One: Mechanisms for
--- 10,15 ----

  This module performs base64 encoding and decoding of arbitrary binary
! strings into text strings that can be safely sent by email or included
! as part of an HTTP POST request.  The
  encoding scheme is defined in \rfc{1521} (\emph{MIME
  (Multipurpose Internet Mail Extensions) Part One: Mechanisms for

Index: libbasehttp.tex
===================================================================
RCS file: /cvsroot/python/python/dist/src/Doc/lib/libbasehttp.tex,v
retrieving revision 1.12
retrieving revision 1.13
diff -C2 -r1.12 -r1.13
*** libbasehttp.tex	2000/10/10 16:56:41	1.12
--- libbasehttp.tex	2001/07/14 02:50:55	1.13
***************
*** 13,24 ****

  This module defines two classes for implementing HTTP servers
! (web servers). Usually, this module isn't used directly, but is used
! as a basis for building functioning web servers. See the
  \module{SimpleHTTPServer}\refstmodindex{SimpleHTTPServer} and
  \refmodule{CGIHTTPServer}\refstmodindex{CGIHTTPServer} modules.

  The first class, \class{HTTPServer}, is a
! \class{SocketServer.TCPServer} subclass. It creates and listens at the
! web socket, dispatching the requests to a handler. Code to create and
  run the server looks like this:

--- 13,24 ----

  This module defines two classes for implementing HTTP servers
! (Web servers). Usually, this module isn't used directly, but is used
! as a basis for building functioning Web servers. See the
  \module{SimpleHTTPServer}\refstmodindex{SimpleHTTPServer} and
  \refmodule{CGIHTTPServer}\refstmodindex{CGIHTTPServer} modules.

  The first class, \class{HTTPServer}, is a
! \class{SocketServer.TCPServer} subclass.  It creates and listens at the
! HTTP socket, dispatching the requests to a handler.  Code to create and
  run the server looks like this:

Index: libcgi.tex
===================================================================
RCS file: /cvsroot/python/python/dist/src/Doc/lib/libcgi.tex,v
retrieving revision 1.30
retrieving revision 1.31
diff -C2 -r1.30 -r1.31
*** libcgi.tex	2001/07/06 19:28:48	1.30
--- libcgi.tex	2001/07/14 02:50:55	1.31
***************
*** 13,17 ****

! Support module for CGI (Common Gateway Interface) scripts.%
  \index{Common Gateway Interface}

--- 13,17 ----

! Support module for Common Gateway Interface (CGI) scripts.%
  \index{Common Gateway Interface}

***************
*** 295,299 ****
  with similar functionality), make very sure you don't pass arbitrary
  strings received from the client to the shell.  This is a well-known
! security hole whereby clever hackers anywhere on the web can exploit a
  gullible CGI script to invoke arbitrary shell commands.  Even parts of
  the URL or field names cannot be trusted, since the request doesn't
--- 295,299 ----
  with similar functionality), make very sure you don't pass arbitrary
  strings received from the client to the shell.  This is a well-known
! security hole whereby clever hackers anywhere on the Web can exploit a
  gullible CGI script to invoke arbitrary shell commands.  Even parts of
  the URL or field names cannot be trusted, since the request doesn't
***************
*** 331,335 ****
  current directory at execution time is also different (it is usually
  the server's cgi-bin directory) and the set of environment variables
! is also different from what you get at login.  In particular, don't
  count on the shell's search path for executables (\envvar{PATH}) or
  the Python module search path (\envvar{PYTHONPATH}) to be set to
--- 331,335 ----
  current directory at execution time is also different (it is usually
  the server's cgi-bin directory) and the set of environment variables
! is also different from what you get when you log in.  In particular, don't
  count on the shell's search path for executables (\envvar{PATH}) or
  the Python module search path (\envvar{PYTHONPATH}) to be set to

Index: libfl.tex
===================================================================
RCS file: /cvsroot/python/python/dist/src/Doc/lib/libfl.tex,v
retrieving revision 1.18
retrieving revision 1.19
diff -C2 -r1.18 -r1.19
*** libfl.tex	1999/04/29 18:42:18	1.18
--- libfl.tex	2001/07/14 02:50:55	1.19
***************
*** 1,8 ****
  \section{\module{fl} ---
!          FORMS library interface for GUI applications}

  \declaremodule{builtin}{fl}
    \platform{IRIX}
! \modulesynopsis{FORMS library interface for GUI applications.}

--- 1,9 ----
  \section{\module{fl} ---
!          FORMS library for graphical user interfaces}

  \declaremodule{builtin}{fl}
    \platform{IRIX}
! \modulesynopsis{FORMS library for applications with graphical user
!                 interfaces.}

Index: libformatter.tex
===================================================================
RCS file: /cvsroot/python/python/dist/src/Doc/lib/libformatter.tex,v
retrieving revision 1.20
retrieving revision 1.21
diff -C2 -r1.20 -r1.21
*** libformatter.tex	2000/07/16 19:01:09	1.20
--- libformatter.tex	2001/07/14 02:50:55	1.21
***************
*** 201,205 ****
  applicability to many writers, and may be used directly in most
  circumstances.  It has been used to implement a full-featured
! world-wide web browser.
  \end{classdesc}

--- 201,205 ----
  applicability to many writers, and may be used directly in most
  circumstances.  It has been used to implement a full-featured
! World Wide Web browser.
  \end{classdesc}

Index: libintro.tex
===================================================================
RCS file: /cvsroot/python/python/dist/src/Doc/lib/libintro.tex,v
retrieving revision 1.7
retrieving revision 1.8
diff -C2 -r1.7 -r1.8
*** libintro.tex	2000/07/16 19:01:09	1.7
--- libintro.tex	2001/07/14 02:50:55	1.8
***************
*** 25,29 ****
  operating systems, such as access to specific hardware; others provide
  interfaces that are
! specific to a particular application domain, like the World-Wide Web.
  Some modules are available in all versions and ports of Python; others
  are only available when the underlying system supports or requires
--- 25,29 ----
  operating systems, such as access to specific hardware; others provide
  interfaces that are
! specific to a particular application domain, like the World Wide Web.
  Some modules are available in all versions and ports of Python; others
  are only available when the underlying system supports or requires

Index: libos.tex
===================================================================
RCS file: /cvsroot/python/python/dist/src/Doc/lib/libos.tex,v
retrieving revision 1.59
retrieving revision 1.60
diff -C2 -r1.59 -r1.60
*** libos.tex	2001/07/06 20:30:11	1.59
--- libos.tex	2001/07/14 02:50:55	1.60
***************
*** 1,16 ****
  \section{\module{os} ---
!          Miscellaneous OS interfaces}

  \declaremodule{standard}{os}
! \modulesynopsis{Miscellaneous OS interfaces.}

  This module provides a more portable way of using operating system
! (OS) dependent functionality than importing an OS dependent built-in
! module like \refmodule{posix} or \module{nt}.

! This module searches for an OS dependent built-in module like
  \module{mac} or \refmodule{posix} and exports the same functions and data
! as found there.  The design of all Python's built-in OS dependent
  modules is such that as long as the same functionality is available,
  it uses the same interface; for example, the function
--- 1,16 ----
  \section{\module{os} ---
!          Miscellaneous operating system interfaces}

  \declaremodule{standard}{os}
! \modulesynopsis{Miscellaneous operating system interfaces.}

  This module provides a more portable way of using operating system
! dependent functionality than importing a operating system dependent
! built-in module like \refmodule{posix} or \module{nt}.

! This module searches for an operating system dependent built-in module like
  \module{mac} or \refmodule{posix} and exports the same functions and data
! as found there.  The design of all Python's built-in operating system dependent
  modules is such that as long as the same functionality is available,
  it uses the same interface; for example, the function
***************
*** 19,30 ****
  \POSIX{} interface).

! Extensions peculiar to a particular OS are also available through the
! \module{os} module, but using them is of course a threat to
! portability!

  Note that after the first time \module{os} is imported, there is
  \emph{no} performance penalty in using functions from \module{os}
! instead of directly from the OS dependent built-in module, so there
! should be \emph{no} reason not to use \module{os}!

--- 19,30 ----
  \POSIX{} interface).

! Extensions peculiar to a particular operating system are also
! available through the \module{os} module, but using them is of course a
! threat to portability!

  Note that after the first time \module{os} is imported, there is
  \emph{no} performance penalty in using functions from \module{os}
! instead of directly from the operating system dependent built-in module,
! so there should be \emph{no} reason not to use \module{os}!

***************
*** 66,76 ****

  \begin{datadesc}{name}
! The name of the OS dependent module imported.  The following names
! have currently been registered: \code{'posix'}, \code{'nt'},
  \code{'dos'}, \code{'mac'}, \code{'os2'}, \code{'ce'}, \code{'java'}.
  \end{datadesc}

  \begin{datadesc}{path}
! The corresponding OS dependent standard module for pathname
  operations, such as \module{posixpath} or \module{macpath}.  Thus,
  given the proper imports, \code{os.path.split(\var{file})} is
--- 66,76 ----

  \begin{datadesc}{name}
! The name of the operating system dependent module imported.  The
! following names have currently been registered: \code{'posix'}, \code{'nt'},
  \code{'dos'}, \code{'mac'}, \code{'os2'}, \code{'ce'}, \code{'java'}.
  \end{datadesc}

  \begin{datadesc}{path}
! The corresponding operating system dependent standard module for pathname
  operations, such as \module{posixpath} or \module{macpath}.  Thus,
  given the proper imports, \code{os.path.split(\var{file})} is
***************
*** 637,641 ****
  \var{name} specifies the configuration value to retrieve; it may be a
  string which is the name of a defined system value; these names are
! specified in a number of standards (\POSIX.1, Unix95, Unix98, and
  others).  Some platforms define additional names as well.  The names
  known to the host operating system are given in the
--- 637,641 ----
  \var{name} specifies the configuration value to retrieve; it may be a
  string which is the name of a defined system value; these names are
! specified in a number of standards (\POSIX.1, \UNIX 95, \UNIX 98, and
  others).  Some platforms define additional names as well.  The names
  known to the host operating system are given in the
***************
*** 738,744 ****
  \code{st_ctime}.
  More items may be added at the end by some implementations.  Note that
! on the Macintosh, the time values are floating point values, like all
! time values on the Macintosh.
! (On MS Windows, some items are filled with dummy values.)
  Availability: Macintosh, \UNIX{}, Windows.

--- 738,744 ----
  \code{st_ctime}.
  More items may be added at the end by some implementations.  Note that
! on the Mac OS, the time values are floating point values, like all
! time values on the Mac OS.
! (On Windows, some items are filled with dummy values.)
  Availability: Macintosh, \UNIX{}, Windows.

***************
*** 984,989 ****
  Start a file with its associated application.  This acts like
  double-clicking the file in Windows Explorer, or giving the file name
! as an argument to the DOS \program{start} command: the file is opened
! with whatever application (if any) its extension is associated.

  \function{startfile()} returns as soon as the associated application
--- 984,990 ----
  Start a file with its associated application.  This acts like
  double-clicking the file in Windows Explorer, or giving the file name
! as an argument to the \program{start} command from the interactive
! command shell: the file is opened with whatever application (if any)
! its extension is associated.

  \function{startfile()} returns as soon as the associated application
***************
*** 1013,1018 ****

  \begin{funcdesc}{times}{}
! Return a 5-tuple of floating point numbers indicating accumulated (CPU
! or other)
  times, in seconds.  The items are: user time, system time, children's
  user time, children's system time, and elapsed real time since a fixed
--- 1014,1019 ----

  \begin{funcdesc}{times}{}
! Return a 5-tuple of floating point numbers indicating accumulated
! (processor or other)
  times, in seconds.  The items are: user time, system time, children's
  user time, children's system time, and elapsed real time since a fixed
***************
*** 1101,1105 ****
  \var{name} specifies the configuration value to retrieve; it may be a
  string which is the name of a defined system value; these names are
! specified in a number of standards (\POSIX, Unix95, Unix98, and
  others).  Some platforms define additional names as well.  The names
  known to the host operating system are given in the
--- 1102,1106 ----
  \var{name} specifies the configuration value to retrieve; it may be a
  string which is the name of a defined system value; these names are
! specified in a number of standards (\POSIX, \UNIX 95, \UNIX 98, and
  others).  Some platforms define additional names as well.  The names
  known to the host operating system are given in the
***************
*** 1152,1166 ****

  \begin{datadesc}{curdir}
! The constant string used by the OS to refer to the current directory.
  For example: \code{'.'} for \POSIX{} or \code{':'} for the Macintosh.
  \end{datadesc}

  \begin{datadesc}{pardir}
! The constant string used by the OS to refer to the parent directory.
  For example: \code{'..'} for \POSIX{} or \code{'::'} for the Macintosh.
  \end{datadesc}

  \begin{datadesc}{sep}
! The character used by the OS to separate pathname components,
  for example, \character{/} for \POSIX{} or \character{:} for the
  Macintosh.  Note that knowing this is not sufficient to be able to
--- 1153,1169 ----

  \begin{datadesc}{curdir}
! The constant string used by the operating system to refer to the current
! directory.
  For example: \code{'.'} for \POSIX{} or \code{':'} for the Macintosh.
  \end{datadesc}

  \begin{datadesc}{pardir}
! The constant string used by the operating system to refer to the parent
! directory.
  For example: \code{'..'} for \POSIX{} or \code{'::'} for the Macintosh.
  \end{datadesc}

  \begin{datadesc}{sep}
! The character used by the operating system to separate pathname components,
  for example, \character{/} for \POSIX{} or \character{:} for the
  Macintosh.  Note that knowing this is not sufficient to be able to
***************
*** 1170,1182 ****

  \begin{datadesc}{altsep}
! An alternative character used by the OS to separate pathname components,
! or \code{None} if only one separator character exists.  This is set to
! \character{/} on DOS and Windows systems where \code{sep} is a backslash.
  \end{datadesc}

  \begin{datadesc}{pathsep}
! The character conventionally used by the OS to separate search patch
! components (as in \envvar{PATH}), such as \character{:} for \POSIX{} or
! \character{;} for DOS and Windows.
  \end{datadesc}

--- 1173,1186 ----

  \begin{datadesc}{altsep}
! An alternative character used by the operating system to separate pathname
! components, or \code{None} if only one separator character exists.  This is
! set to \character{/} on DOS and Windows systems where \code{sep} is a
! backslash.
  \end{datadesc}

  \begin{datadesc}{pathsep}
! The character conventionally used by the operating system to separate
! search patch components (as in \envvar{PATH}), such as \character{:} for
! \POSIX{} or \character{;} for DOS and Windows.
  \end{datadesc}

***************
*** 1189,1193 ****
  The string used to separate (or, rather, terminate) lines on the
  current platform.  This may be a single character, such as \code{'\e
! n'} for \POSIX{} or \code{'\e r'} for MacOS, or multiple characters,
! for example, \code{'\e r\e n'} for MS-DOS and MS Windows.
  \end{datadesc}
--- 1193,1197 ----
  The string used to separate (or, rather, terminate) lines on the
  current platform.  This may be a single character, such as \code{'\e
! n'} for \POSIX{} or \code{'\e r'} for the Mac OS, or multiple characters,
! for example, \code{'\e r\e n'} for DOS and Windows.
  \end{datadesc}

Index: libpanel.tex
===================================================================
RCS file: /cvsroot/python/python/dist/src/Doc/lib/libpanel.tex,v
retrieving revision 1.10
retrieving revision 1.11
diff -C2 -r1.10 -r1.11
*** libpanel.tex	2000/07/16 19:01:09	1.10
--- libpanel.tex	2001/07/14 02:50:55	1.11
***************
*** 61,65 ****
  This module provides access to the
  \emph{Panel Library}
! built by NASA Ames\index{NASA} (to get it, send e-mail to
  \code{panel-request@nas.nasa.gov}).
  All access to it should be done through the standard module
--- 61,65 ----
  This module provides access to the
  \emph{Panel Library}
! built by NASA Ames\index{NASA} (to get it, send email to
  \code{panel-request@nas.nasa.gov}).
  All access to it should be done through the standard module

Index: libresource.tex
===================================================================
RCS file: /cvsroot/python/python/dist/src/Doc/lib/libresource.tex,v
retrieving revision 1.13
retrieving revision 1.14
diff -C2 -r1.13 -r1.14
*** libresource.tex	1999/03/02 17:03:40	1.13
--- libresource.tex	2001/07/14 02:50:55	1.14
***************
*** 78,82 ****

  \begin{datadesc}{RLIMIT_CPU}
!   The maximum amount of CPU time (in seconds) that a process can
    use. If this limit is exceeded, a \constant{SIGXCPU} signal is sent to
    the process. (See the \refmodule{signal} module documentation for
--- 78,82 ----

  \begin{datadesc}{RLIMIT_CPU}
!   The maximum amount of processor time (in seconds) that a process can
    use. If this limit is exceeded, a \constant{SIGXCPU} signal is sent to
    the process. (See the \refmodule{signal} module documentation for

Index: librestricted.tex
===================================================================
RCS file: /cvsroot/python/python/dist/src/Doc/lib/librestricted.tex,v
retrieving revision 1.6
retrieving revision 1.7
diff -C2 -r1.6 -r1.7
*** librestricted.tex	1999/04/23 17:26:24	1.6
--- librestricted.tex	2001/07/14 02:50:55	1.7
***************
*** 5,13 ****
  example, a Python program can open any file for reading and writing by
  using the \function{open()} built-in function (provided the underlying
! OS gives you permission!).  This is exactly what you want for most
! applications.

  There exists a class of applications for which this ``openness'' is
! inappropriate.  Take Grail: a web browser that accepts ``applets,''
  snippets of Python code, from anywhere on the Internet for execution
  on the local system.  This can be used to improve the user interface
--- 5,13 ----
  example, a Python program can open any file for reading and writing by
  using the \function{open()} built-in function (provided the underlying
! operating system gives you permission!).  This is exactly what you want
! for most applications.

  There exists a class of applications for which this ``openness'' is
! inappropriate.  Take Grail: a Web browser that accepts ``applets,''
  snippets of Python code, from anywhere on the Internet for execution
  on the local system.  This can be used to improve the user interface

Index: librexec.tex
===================================================================
RCS file: /cvsroot/python/python/dist/src/Doc/lib/librexec.tex,v
retrieving revision 1.16
retrieving revision 1.17
diff -C2 -r1.16 -r1.17
*** librexec.tex	2001/07/06 20:30:11	1.16
--- librexec.tex	2001/07/14 02:50:55	1.17
***************
*** 19,23 ****
  unsafe operations like reading or writing disk files, or using TCP/IP
  sockets.  However, it does not protect against code using extremely
! large amounts of memory or CPU time.  

  \begin{classdesc}{RExec}{\optional{hooks\optional{, verbose}}}
--- 19,23 ----
  unsafe operations like reading or writing disk files, or using TCP/IP
  sockets.  However, it does not protect against code using extremely
! large amounts of memory or processor time.  

  \begin{classdesc}{RExec}{\optional{hooks\optional{, verbose}}}

Index: librobotparser.tex
===================================================================
RCS file: /cvsroot/python/python/dist/src/Doc/lib/librobotparser.tex,v
retrieving revision 1.2
retrieving revision 1.3
diff -C2 -r1.2 -r1.3
*** librobotparser.tex	2000/04/28 18:17:23	1.2
--- librobotparser.tex	2001/07/14 02:50:55	1.3
***************
*** 10,14 ****

  \index{WWW}
! \index{World-Wide Web}
  \index{URL}
  \index{robots.txt}
--- 10,14 ----

  \index{WWW}
! \index{World Wide Web}
  \index{URL}
  \index{robots.txt}
***************
*** 16,20 ****
  This module provides a single class, \class{RobotFileParser}, which answers
  questions about whether or not a particular user agent can fetch a URL on
! the web site that published the \file{robots.txt} file.  For more details on 
  the structure of \file{robots.txt} files, see
  \url{http://info.webcrawler.com/mak/projects/robots/norobots.html}. 
--- 16,20 ----
  This module provides a single class, \class{RobotFileParser}, which answers
  questions about whether or not a particular user agent can fetch a URL on
! the Web site that published the \file{robots.txt} file.  For more details on 
  the structure of \file{robots.txt} files, see
  \url{http://info.webcrawler.com/mak/projects/robots/norobots.html}. 

Index: libstdwin.tex
===================================================================
RCS file: /cvsroot/python/python/dist/src/Doc/lib/libstdwin.tex,v
retrieving revision 1.23
retrieving revision 1.24
diff -C2 -r1.23 -r1.24
*** libstdwin.tex	2000/07/16 19:01:10	1.23
--- libstdwin.tex	2001/07/14 02:50:55	1.24
***************
*** 17,24 ****

  \section{\module{stdwin} ---
!          Platform-independent GUI System}

  \declaremodule{builtin}{stdwin}
! \modulesynopsis{Older GUI system for X11 and Macintosh.}

--- 17,24 ----

  \section{\module{stdwin} ---
!          Platform-independent Graphical User Interface System}

  \declaremodule{builtin}{stdwin}
! \modulesynopsis{Older graphical user interface system for X11 and Macintosh.}

Index: libtime.tex
===================================================================
RCS file: /cvsroot/python/python/dist/src/Doc/lib/libtime.tex,v
retrieving revision 1.40
retrieving revision 1.41
diff -C2 -r1.40 -r1.41
*** libtime.tex	2001/07/06 20:30:11	1.40
--- libtime.tex	2001/07/14 02:50:55	1.41
***************
*** 127,135 ****

  \begin{funcdesc}{clock}{}
! Return the current CPU time as a floating point number expressed in
  seconds.  The precision, and in fact the very definition of the meaning
! of ``CPU time''\index{CPU time}, depends on that of the C function
! of the same name, but in any case, this is the function to use for
! benchmarking\index{benchmarking} Python or timing algorithms.
  \end{funcdesc}

--- 127,136 ----

  \begin{funcdesc}{clock}{}
! Return the current processor time as a floating point number expressed in
  seconds.  The precision, and in fact the very definition of the meaning
! of ``processor time''\index{CPU time}\index{processor time}, depends on
! that of the C function of the same name, but in any case, this is the
! function to use for benchmarking\index{benchmarking} Python or timing
! algorithms.
  \end{funcdesc}

Index: libunittest.tex
===================================================================
RCS file: /cvsroot/python/python/dist/src/Doc/lib/libunittest.tex,v
retrieving revision 1.4
retrieving revision 1.5
diff -C2 -r1.4 -r1.5
*** libunittest.tex	2001/04/12 19:34:38	1.4
--- libunittest.tex	2001/07/14 02:50:55	1.5
***************
*** 628,632 ****
  maintain the internal data structures, and mmay be extended in
  subclasses to support additional reporting requirements.  This is
! particularly useful in building GUI tools which support interactive
  reporting while tests are being run.

--- 628,632 ----
  maintain the internal data structures, and mmay be extended in
  subclasses to support additional reporting requirements.  This is
! particularly useful in building tools which support interactive
  reporting while tests are being run.

***************
*** 668,673 ****
    additional tests.  This is used by the \class{TextTestRunner} class
    to stop the test framework when the user signals an interrupt from
!   the keyboard.  GUI tools which provide runners can use this in a
!   similar manner.
  \end{methoddesc}

--- 668,673 ----
    additional tests.  This is used by the \class{TextTestRunner} class
    to stop the test framework when the user signals an interrupt from
!   the keyboard.  Interactive tools which provide runners can use this
!   in a similar manner.
  \end{methoddesc}

Index: liburllib.tex
===================================================================
RCS file: /cvsroot/python/python/dist/src/Doc/lib/liburllib.tex,v
retrieving revision 1.35
retrieving revision 1.36
diff -C2 -r1.35 -r1.36
*** liburllib.tex	2001/04/12 20:26:49	1.35
--- liburllib.tex	2001/07/14 02:50:55	1.36
***************
*** 6,15 ****

  \index{WWW}
! \index{World-Wide Web}
  \index{URL}

  This module provides a high-level interface for fetching data across
! the World-Wide Web.  In particular, the \function{urlopen()} function
  is similar to the built-in function \function{open()}, but accepts
  Universal Resource Locators (URLs) instead of filenames.  Some
--- 6,15 ----

  \index{WWW}
! \index{World Wide Web}
  \index{URL}

  This module provides a high-level interface for fetching data across
! the World Wide Web.  In particular, the \function{urlopen()} function
  is similar to the built-in function \function{open()}, but accepts
  Universal Resource Locators (URLs) instead of filenames.  Some
***************
*** 250,254 ****
  cause arbitrarily long delays while waiting for a network connection
  to be set up.  This means that it is difficult to build an interactive
! web client using these functions without using threads.

  \item
--- 250,254 ----
  cause arbitrarily long delays while waiting for a network connection
  to be set up.  This means that it is difficult to build an interactive
! Web client using these functions without using threads.

  \item

Index: liburlparse.tex
===================================================================
RCS file: /cvsroot/python/python/dist/src/Doc/lib/liburlparse.tex,v
retrieving revision 1.18
retrieving revision 1.19
diff -C2 -r1.18 -r1.19
*** liburlparse.tex	2000/08/25 17:29:35	1.18
--- liburlparse.tex	2001/07/14 02:50:55	1.19
***************
*** 6,10 ****

  \index{WWW}
! \index{World-Wide Web}
  \index{URL}
  \indexii{URL}{parsing}
--- 6,10 ----

  \index{WWW}
! \index{World Wide Web}
  \index{URL}
  \indexii{URL}{parsing}

Index: libxmllib.tex
===================================================================
RCS file: /cvsroot/python/python/dist/src/Doc/lib/libxmllib.tex,v
retrieving revision 1.31
retrieving revision 1.32
diff -C2 -r1.31 -r1.32
*** libxmllib.tex	2001/07/06 20:30:11	1.31
--- libxmllib.tex	2001/07/14 02:50:55	1.32
***************
*** 282,286 ****
  \begin{seealso}
    \seetitle[http://www.w3.org/TR/REC-xml-names/]{Namespaces in XML}{
!            This World-Wide Web Consortium recommendation describes the
             proper syntax and processing requirements for namespaces in
             XML.}
--- 282,286 ----
  \begin{seealso}
    \seetitle[http://www.w3.org/TR/REC-xml-names/]{Namespaces in XML}{
!            This World Wide Web Consortium recommendation describes the
             proper syntax and processing requirements for namespaces in
             XML.}