Lots of minor fixes, many suggested by Detlef Lannert
<lannert@uni-duesseldorf.de>.
This commit is contained in:
parent
0bb0a90b20
commit
d68442b164
|
@ -266,11 +266,11 @@ target: identifier | "(" target_list ")" | "[" target_list "]"
|
||||||
(See section \ref{primaries} for the syntax definitions for the last
|
(See section \ref{primaries} for the syntax definitions for the last
|
||||||
three symbols.)
|
three symbols.)
|
||||||
|
|
||||||
An augmented assignment evaluates the target (which, unlike with normal
|
An augmented assignment evaluates the target (which, unlike normal
|
||||||
assignment statements, cannot be a tuple) and the expression list, performs
|
assignment statements, cannot be an unpacking) and the expression
|
||||||
the binary operation specific to the type of assignment on the two operands,
|
list, performs the binary operation specific to the type of assignment
|
||||||
and assigns the result to the original target. The target is only evaluated
|
on the two operands, and assigns the result to the original
|
||||||
once.
|
target. The target is only evaluated once.
|
||||||
|
|
||||||
An augmented assignment expression like \code{x += 1} can be rewritten as
|
An augmented assignment expression like \code{x += 1} can be rewritten as
|
||||||
\code{x = x + 1} to achieve a similar, but not exactly equal effect. In the
|
\code{x = x + 1} to achieve a similar, but not exactly equal effect. In the
|
||||||
|
@ -370,9 +370,10 @@ exception is raised.
|
||||||
\exindex{RuntimeError}
|
\exindex{RuntimeError}
|
||||||
|
|
||||||
\keyword{print} also has an extended form, defined as
|
\keyword{print} also has an extended form, defined as
|
||||||
|
\index{extended print statement}
|
||||||
|
|
||||||
\begin{verbatim}
|
\begin{verbatim}
|
||||||
print_stmt: '>>' expression [ (',' expression)+ [','] ] )
|
print_stmt: "print" ">>" expression [ ("," expression)+ [","] ]
|
||||||
\end{verbatim}
|
\end{verbatim}
|
||||||
|
|
||||||
In this form, the first expression after the \keyword{>>} must
|
In this form, the first expression after the \keyword{>>} must
|
||||||
|
@ -559,7 +560,7 @@ see below.
|
||||||
The \keyword{from} form does not bind the module name: it goes through the
|
The \keyword{from} form does not bind the module name: it goes through the
|
||||||
list of identifiers, looks each one of them up in the module found in step
|
list of identifiers, looks each one of them up in the module found in step
|
||||||
(1), and binds the name in the local namespace to the object thus found.
|
(1), and binds the name in the local namespace to the object thus found.
|
||||||
Like with the first form of \keyword{import}, an alternate local name can be
|
As with the first form of \keyword{import}, an alternate local name can be
|
||||||
supplied by specifying "\keyword{as} localname". If a name is not found,
|
supplied by specifying "\keyword{as} localname". If a name is not found,
|
||||||
\exception{ImportError} is raised. If the list of identifiers is replaced
|
\exception{ImportError} is raised. If the list of identifiers is replaced
|
||||||
by a star (\samp{*}), all names defined in the module are bound, except
|
by a star (\samp{*}), all names defined in the module are bound, except
|
||||||
|
|
Loading…
Reference in New Issue