Commit 9efcbced authored by Raymond Hettinger's avatar Raymond Hettinger

Fix double word typos.

parent 2f8566d4
...@@ -12,7 +12,7 @@ cookies, an HTTP state management mechanism. It supports both simple ...@@ -12,7 +12,7 @@ cookies, an HTTP state management mechanism. It supports both simple
string-only cookies, and provides an abstraction for having any serializable string-only cookies, and provides an abstraction for having any serializable
data-type as cookie value. data-type as cookie value.
The module formerly strictly applied the parsing rules described in in The module formerly strictly applied the parsing rules described in
the \rfc{2109} and \rfc{2068} specifications. It has since been discovered the \rfc{2109} and \rfc{2068} specifications. It has since been discovered
that MSIE 3.0x doesn't follow the character rules outlined in those that MSIE 3.0x doesn't follow the character rules outlined in those
specs. As a result, the parsing rules used are a bit less strict. specs. As a result, the parsing rules used are a bit less strict.
......
...@@ -422,7 +422,7 @@ class C: ...@@ -422,7 +422,7 @@ class C:
file's desired buffer size: 0 means unbuffered, 1 means line file's desired buffer size: 0 means unbuffered, 1 means line
buffered, any other positive value means use a buffer of buffered, any other positive value means use a buffer of
(approximately) that size. A negative \var{bufsize} means to use (approximately) that size. A negative \var{bufsize} means to use
the system default, which is usually line buffered for for tty the system default, which is usually line buffered for tty
devices and fully buffered for other files. If omitted, the system devices and fully buffered for other files. If omitted, the system
default is used.\footnote{ default is used.\footnote{
Specifying a buffer size currently has no effect on systems that Specifying a buffer size currently has no effect on systems that
......
...@@ -58,7 +58,7 @@ locale.setlocale(locale.LC_ALL, '') ...@@ -58,7 +58,7 @@ locale.setlocale(locale.LC_ALL, '')
\end{funcdesc} \end{funcdesc}
\begin{funcdesc}{localeconv}{} \begin{funcdesc}{localeconv}{}
Returns the database of of the local conventions as a dictionary. Returns the database of the local conventions as a dictionary.
This dictionary has the following strings as keys: This dictionary has the following strings as keys:
\begin{tableiii}{l|l|p{3in}}{constant}{Key}{Category}{Meaning} \begin{tableiii}{l|l|p{3in}}{constant}{Key}{Category}{Meaning}
......
...@@ -72,7 +72,7 @@ mailbox specified by \var{dirname} is made available. ...@@ -72,7 +72,7 @@ mailbox specified by \var{dirname} is made available.
Access a Babyl mailbox, which is similar to an MMDF mailbox. In Access a Babyl mailbox, which is similar to an MMDF mailbox. In
Babyl format, each message has two sets of headers, the Babyl format, each message has two sets of headers, the
\emph{original} headers and the \emph{visible} headers. The original \emph{original} headers and the \emph{visible} headers. The original
headers appear before a a line containing only \code{'*** EOOH ***'} headers appear before a line containing only \code{'*** EOOH ***'}
(End-Of-Original-Headers) and the visible headers appear after the (End-Of-Original-Headers) and the visible headers appear after the
\code{EOOH} line. Babyl-compliant mail readers will show you only the \code{EOOH} line. Babyl-compliant mail readers will show you only the
visible headers, and \class{BabylMailbox} objects will return messages visible headers, and \class{BabylMailbox} objects will return messages
......
...@@ -17,7 +17,7 @@ it can be easily adapted for more general use. ...@@ -17,7 +17,7 @@ it can be easily adapted for more general use.
\begin{classdesc}{MultiFile}{fp\optional{, seekable}} \begin{classdesc}{MultiFile}{fp\optional{, seekable}}
Create a multi-file. You must instantiate this class with an input Create a multi-file. You must instantiate this class with an input
object argument for the \class{MultiFile} instance to get lines from, object argument for the \class{MultiFile} instance to get lines from,
such as as a file object returned by \function{open()}. such as a file object returned by \function{open()}.
\class{MultiFile} only ever looks at the input object's \class{MultiFile} only ever looks at the input object's
\method{readline()}, \method{seek()} and \method{tell()} methods, and \method{readline()}, \method{seek()} and \method{tell()} methods, and
......
...@@ -77,7 +77,7 @@ used. (See the explanation of the \keyword{exec} statement or the ...@@ -77,7 +77,7 @@ used. (See the explanation of the \keyword{exec} statement or the
\end{funcdesc} \end{funcdesc}
\begin{funcdesc}{runeval}{expression\optional{, globals\optional{, locals}}} \begin{funcdesc}{runeval}{expression\optional{, globals\optional{, locals}}}
Evaluate the \var{expression} (given as a a string) under debugger Evaluate the \var{expression} (given as a string) under debugger
control. When \function{runeval()} returns, it returns the value of the control. When \function{runeval()} returns, it returns the value of the
expression. Otherwise this function is similar to expression. Otherwise this function is similar to
\function{run()}. \function{run()}.
......
...@@ -533,7 +533,7 @@ The second limitation has to do with accuracy of timing information. ...@@ -533,7 +533,7 @@ The second limitation has to do with accuracy of timing information.
There is a fundamental problem with deterministic profilers involving There is a fundamental problem with deterministic profilers involving
accuracy. The most obvious restriction is that the underlying ``clock'' accuracy. The most obvious restriction is that the underlying ``clock''
is only ticking at a rate (typically) of about .001 seconds. Hence no is only ticking at a rate (typically) of about .001 seconds. Hence no
measurements will be more accurate that that underlying clock. If measurements will be more accurate than the underlying clock. If
enough measurements are taken, then the ``error'' will tend to average enough measurements are taken, then the ``error'' will tend to average
out. Unfortunately, removing this first error induces a second source out. Unfortunately, removing this first error induces a second source
of error... of error...
......
...@@ -46,7 +46,7 @@ certain stdio libraries in which \cfunction{tell()} discards buffered ...@@ -46,7 +46,7 @@ certain stdio libraries in which \cfunction{tell()} discards buffered
data before discovering that the \cfunction{lseek()} system call data before discovering that the \cfunction{lseek()} system call
doesn't work. For maximum portability, you should set the seekable doesn't work. For maximum portability, you should set the seekable
argument to zero to prevent that initial \method{tell()} when passing argument to zero to prevent that initial \method{tell()} when passing
in an unseekable object such as a a file object created from a socket in an unseekable object such as a file object created from a socket
object. object.
Input lines as read from the file may either be terminated by CR-LF or Input lines as read from the file may either be terminated by CR-LF or
......
...@@ -29,7 +29,7 @@ contents are kept in a regular dictionary, which is accessible via the ...@@ -29,7 +29,7 @@ contents are kept in a regular dictionary, which is accessible via the
\member{data} attribute of \class{UserDict} instances. If \member{data} attribute of \class{UserDict} instances. If
\var{initialdata} is provided, \member{data} is initialized with its \var{initialdata} is provided, \member{data} is initialized with its
contents; note that a reference to \var{initialdata} will not be kept, contents; note that a reference to \var{initialdata} will not be kept,
allowing it be used used for other purposes. allowing it be used for other purposes.
\end{classdesc} \end{classdesc}
In addition to supporting the methods and operations of mappings (see In addition to supporting the methods and operations of mappings (see
......
...@@ -210,7 +210,7 @@ Instances have the following attributes: ...@@ -210,7 +210,7 @@ Instances have the following attributes:
\end{memberdesc} \end{memberdesc}
\begin{memberdesc}[ZipInfo]{date_time} \begin{memberdesc}[ZipInfo]{date_time}
The time and date of the last modification to to the archive The time and date of the last modification to the archive
member. This is a tuple of six values: member. This is a tuple of six values:
\begin{tableii}{c|l}{code}{Index}{Value} \begin{tableii}{c|l}{code}{Index}{Value}
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment