WARNING: Although the definition of assignment implies that overlaps

between the left-hand side and the right-hand side are `safe' (e.g.

collection of assigned-to variables are not safe! For instance, the

\begin{verbatim}

\end{verbatim}

\stindex{pass}

\begin{verbatim}

\end{verbatim}

\stindex{del}

\begin{verbatim}

right type (but even this is determined by the sliced object).

\indexii{attribute}{deletion}

\stindex{print}

\begin{verbatim}

the output system believes it is positioned at the beginning of a

line. This is the case: (1) when no characters have yet been written

to standard output; or (2) when the last character written to standard

output was not a \keyword{print} statement. (In some cases it may be

functional to write an empty string to standard output for this

reason.)

\index{output}

\indexii{writing}{values}

statement ends with a comma. This is the only action if the statement

contains just the keyword \keyword{print}.

\indexii{trailing}{comma}

\indexii{newline}{suppression}

or if it is not a writable file, a \exception{RuntimeError} exception is raised.

(The original implementation attempts to write to the system's original

standard output instead, but this is not safe, and should be fixed.)

\ttindex{stdout}

\exindex{RuntimeError}

\stindex{return}

\begin{verbatim}

before really leaving the function.

\kwindex{finally}

\stindex{raise}

\begin{verbatim}

transparently in an except clause.

\obindex{traceback}

\stindex{break}

\begin{verbatim}

before really leaving the loop.

\kwindex{finally}

\stindex{continue}

\begin{verbatim}

\keyword{continue} may only occur syntactically nested in a \keyword{for} or

\keyword{while} loop, but not nested in a function or class definition or

\keyword{try} statement within that loop.\footnote{Except that it may

\stindex{for}

\stindex{while}

\indexii{loop}{statement}

\kwindex{finally}

It continues with the next cycle of the nearest enclosing loop.

\stindex{import}

\begin{verbatim}

\indexii{built-in}{module}

\indexii{user-defined}{module}

\refbimodindex{sys}

\indexii{filename}{extension}

If a built-in module is found, its built-in initialization code is

executed and step (1) is finished. If no matching file is found,

of them up in the module found in step (1), and binds the name in the

local name space to the object thus found. If a name is not found,

\exception{ImportError} is raised. If the list of identifiers is replaced

\indexii{name}{binding}

\exindex{ImportError}

Names bound by import statements may not occur in \keyword{global}

statements in the same scope.

\stindex{global}

\kwindex{from}

\ttindex{from ... import *}

implementations may enforce them or silently change the meaning of the

program.)

\stindex{global}

\begin{verbatim}

The \keyword{global} statement is a declaration which holds for the

entire current code block. It means that the listed identifiers are to be

names would be impossible without \keyword{global}.

\indexiii{global}{name}{binding}

Note: the \keyword{global} is a directive to the parser. Therefore, it

applies only to code parsed at the same time as the \keyword{global}

statement. In particular, a \keyword{global} statement contained in an

the \keyword{exec} statement, and code contained in an \keyword{exec}

statement is unaffected by \keyword{global} statements in the code

containing the \keyword{exec} statement. The same applies to the