Patch #821093: Fix various typos.
This commit is contained in:
parent
dd7eb146a8
commit
95cf84a4f3
|
@ -1112,7 +1112,7 @@ These are the UTF-16 codec APIs:
|
|||
|
||||
% --- Unicode-Escape Codecs ----------------------------------------------
|
||||
|
||||
These are the ``Unicode Esacpe'' codec APIs:
|
||||
These are the ``Unicode Escape'' codec APIs:
|
||||
|
||||
\begin{cfuncdesc}{PyObject*}{PyUnicode_DecodeUnicodeEscape}{const char *s,
|
||||
int size,
|
||||
|
@ -1138,13 +1138,13 @@ These are the ``Unicode Esacpe'' codec APIs:
|
|||
|
||||
% --- Raw-Unicode-Escape Codecs ------------------------------------------
|
||||
|
||||
These are the ``Raw Unicode Esacpe'' codec APIs:
|
||||
These are the ``Raw Unicode Escape'' codec APIs:
|
||||
|
||||
\begin{cfuncdesc}{PyObject*}{PyUnicode_DecodeRawUnicodeEscape}{const char *s,
|
||||
int size,
|
||||
const char *errors}
|
||||
Creates a Unicode object by decoding \var{size} bytes of the
|
||||
Raw-Unicode-Esacpe encoded string \var{s}. Returns \NULL{} if an
|
||||
Raw-Unicode-Escape encoded string \var{s}. Returns \NULL{} if an
|
||||
exception was raised by the codec.
|
||||
\end{cfuncdesc}
|
||||
|
||||
|
@ -1325,7 +1325,7 @@ machine running the codec.
|
|||
|
||||
The following APIs are capable of handling Unicode objects and strings
|
||||
on input (we refer to them as strings in the descriptions) and return
|
||||
Unicode objects or integers as apporpriate.
|
||||
Unicode objects or integers as appropriate.
|
||||
|
||||
They all return \NULL{} or \code{-1} if an exception occurs.
|
||||
|
||||
|
|
|
@ -752,7 +752,7 @@ previous versions.
|
|||
function when an exception has been raised. The callback function
|
||||
is called with this value for \var{what} when after any bytecode is
|
||||
processed after which the exception becomes set within the frame
|
||||
being executed. The effect of this is that as exception propogation
|
||||
being executed. The effect of this is that as exception propagation
|
||||
causes the Python stack to unwind, the callback is called upon
|
||||
return to each frame as the exception propagates. Only trace
|
||||
functions receives these events; they are not needed by the
|
||||
|
@ -767,7 +767,7 @@ previous versions.
|
|||
|
||||
\begin{cvardesc}{int}{PyTrace_RETURN}
|
||||
The value for the \var{what} parameter to \ctype{Py_tracefunc}
|
||||
functions when a call is returning without propogating an exception.
|
||||
functions when a call is returning without propagating an exception.
|
||||
\end{cvardesc}
|
||||
|
||||
\begin{cfuncdesc}{void}{PyEval_SetProfile}{Py_tracefunc func, PyObject *obj}
|
||||
|
|
|
@ -498,7 +498,7 @@ Foo_Type.ob_type = &PyType_Type;
|
|||
|
||||
The destructor function is called by the \cfunction{Py_DECREF()} and
|
||||
\cfunction{Py_XDECREF()} macros when the new reference count is
|
||||
zero. At this point, the instance is still in existance, but there
|
||||
zero. At this point, the instance is still in existence, but there
|
||||
are no references to it. The destructor function should free all
|
||||
references which the instance owns, free all memory buffers owned by
|
||||
the instance (using the freeing function corresponding to the
|
||||
|
@ -1515,7 +1515,7 @@ to be able to test for its presence before using it.}
|
|||
\label{supporting-iteration}}
|
||||
|
||||
|
||||
\section{Supporting Cyclic Garbarge Collection
|
||||
\section{Supporting Cyclic Garbage Collection
|
||||
\label{supporting-cycle-detection}}
|
||||
|
||||
Python's support for detecting and collecting garbage which involves
|
||||
|
|
|
@ -805,7 +805,7 @@ On the other hand, this doesn't help the developer to find the cause
|
|||
of the failure. For this purpose, the DISTUTILS_DEBUG environment
|
||||
variable can be set to anything except an empty string, and distutils
|
||||
will now print detailed information what it is doing, and prints the
|
||||
full traceback in case an exception occurrs.
|
||||
full traceback in case an exception occurs.
|
||||
|
||||
\section{Writing the Setup Configuration File}
|
||||
\label{setup-config}
|
||||
|
|
|
@ -158,7 +158,7 @@ python setup.py install
|
|||
On Windows, you'd probably download \file{foo-1.0.zip}. If you
|
||||
downloaded the archive file to \file{C:\textbackslash{}Temp}, then it
|
||||
would unpack into \file{C:\textbackslash{}Temp\textbackslash{}foo-1.0};
|
||||
you can use either a archive manipulator with a grapical user interface
|
||||
you can use either a archive manipulator with a graphical user interface
|
||||
(such as WinZip) or a command-line tool (such as \program{unzip} or
|
||||
\program{pkunzip}) to unpack the archive. Then, open a command prompt
|
||||
window (``DOS box''), and run:
|
||||
|
|
|
@ -1034,7 +1034,7 @@ base class has an \method{__init__()} method, the derived class's
|
|||
\method{__init__()} method, if any, must explicitly call it to ensure proper
|
||||
initialization of the base class part of the instance; for example:
|
||||
\samp{BaseClass.__init__(\var{self}, [\var{args}...])}. As a special
|
||||
contraint on constructors, no value may be returned; doing so will
|
||||
constraint on constructors, no value may be returned; doing so will
|
||||
cause a \exception{TypeError} to be raised at runtime.
|
||||
\end{methoddesc}
|
||||
|
||||
|
|
|
@ -1004,7 +1004,7 @@ not \code{''}.)
|
|||
\section{Lambdas\label{lambdas}}
|
||||
\indexii{lambda}{expression}
|
||||
\indexii{lambda}{form}
|
||||
\indexii{anonmymous}{function}
|
||||
\indexii{anonymous}{function}
|
||||
|
||||
Lambda forms (lambda expressions) have the same syntactic position as
|
||||
expressions. They are a shorthand to create anonymous functions; the
|
||||
|
|
|
@ -2494,7 +2494,7 @@ interpreter; these provide access to operations that are not part of
|
|||
the core of the language but are nevertheless built in, either for
|
||||
efficiency or to provide access to operating system primitives such as
|
||||
system calls. The set of such modules is a configuration option which
|
||||
also dependson the underlying platform For example,
|
||||
also depends on the underlying platform For example,
|
||||
the \module{amoeba} module is only provided on systems that somehow
|
||||
support Amoeba primitives. One particular module deserves some
|
||||
attention: \ulink{\module{sys}}{../lib/module-sys.html}%
|
||||
|
@ -2647,7 +2647,7 @@ Sound/ Top-level package
|
|||
...
|
||||
\end{verbatim}
|
||||
|
||||
When importing the package, Python searchs through the directories
|
||||
When importing the package, Python searches through the directories
|
||||
on \code{sys.path} looking for the package subdirectory.
|
||||
|
||||
The \file{__init__.py} files are required to make Python treat the
|
||||
|
|
Loading…
Reference in New Issue