Don't say that the module defines the "following functions" and then

only describe one; say "following function" instead!

Merge the two one-sentence paragraphs into a single paragraph, so it
doesn't look too stupid.
This commit is contained in:
Fred Drake 1999-01-27 15:48:23 +00:00
parent 5763e07ea3
commit da452bf6a7

View file

@ -6,9 +6,7 @@
The \code{code} module defines operations pertaining to Python code The \code{code} module defines operations pertaining to Python code
objects. objects. It defines the following function:
The \code{code} module defines the following functions:
\begin{funcdesc}{compile_command}{source, \optional{filename\optional{, symbol}}} \begin{funcdesc}{compile_command}{source, \optional{filename\optional{, symbol}}}
@ -21,14 +19,12 @@ the same decision as the real interpreter main loop.
Arguments: \var{source} is the source string; \var{filename} is the Arguments: \var{source} is the source string; \var{filename} is the
optional filename from which source was read, defaulting to optional filename from which source was read, defaulting to
\code{"<input>"}; and \var{symbol} is the optional grammar start \code{'<input>'}; and \var{symbol} is the optional grammar start
symbol, which should be either \code{"single"} (the default) or symbol, which should be either \code{'single'} (the default) or
\code{"eval"}. \code{'eval'}.
Return a code object (the same as \code{compile(\var{source}, Return a code object (the same as \code{compile(\var{source},
\var{filename}, \var{symbol})}) if the command is complete and valid; \var{filename}, \var{symbol})}) if the command is complete and valid;
return \code{None} if the command is incomplete; raise return \code{None} if the command is incomplete; raise
\code{SyntaxError} if the command is a syntax error. \exception{SyntaxError} if the command is a syntax error.
\end{funcdesc} \end{funcdesc}