[Python-checkins] python/dist/src/Doc/dist dist.tex,1.86,1.87
rhettinger at users.sourceforge.net
rhettinger at users.sourceforge.net
Sat Jan 1 01:29:02 CET 2005
Update of /cvsroot/python/python/dist/src/Doc/dist
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv3901/Doc/dist
Modified Files:
dist.tex
Log Message:
SF Patch #1093896: miscellaneous doc typos
Index: dist.tex
===================================================================
RCS file: /cvsroot/python/python/dist/src/Doc/dist/dist.tex,v
retrieving revision 1.86
retrieving revision 1.87
diff -u -d -r1.86 -r1.87
--- dist.tex 25 Aug 2004 14:01:32 -0000 1.86
+++ dist.tex 1 Jan 2005 00:28:29 -0000 1.87
@@ -34,7 +34,7 @@
build/release/install mechanics.
\end{abstract}
-% The ugly "%begin{latexonly}" pseudo-environment supresses the table
+% The ugly "%begin{latexonly}" pseudo-environment suppresses the table
% of contents for HTML generation.
%
%begin{latexonly}
@@ -965,7 +965,7 @@
\end{verbatim}
This will affect all builds of this module distribution, whether or not
-you explcitly specify \command{build\_ext}. If you include
+you explicitly specify \command{build\_ext}. If you include
\file{setup.cfg} in your source distribution, it will also affect
end-user builds---which is probably a bad idea for this option, since
always building extensions in-place would break installation of the
@@ -2521,7 +2521,7 @@
\var{extra_preargs} and \var{extra_postargs} are implementation- dependent.
On platforms that have the notion of a command-line (e.g. \UNIX,
DOS/Windows), they are most likely lists of strings: extra
-command-line arguments to prepand/append to the compiler command
+command-line arguments to prepend/append to the compiler command
line. On other platforms, consult the implementation class
documentation. In any event, they are intended as an escape hatch
for those occasions when the abstract compiler framework doesn't
More information about the Python-checkins
mailing list