mirror of
https://github.com/python/cpython.git
synced 2025-11-02 03:01:58 +00:00
Lots of small corrections by Andrew Kuchling (plus all new rotor docs)
This commit is contained in:
parent
4b4c664d2e
commit
16d6e7109d
62 changed files with 520 additions and 282 deletions
|
|
@ -9,7 +9,7 @@
|
|||
E-mail: {\tt guido@cwi.nl}
|
||||
}
|
||||
|
||||
\date{14 Jul 1994 \\ Release 1.0.3} % XXX update before release!
|
||||
\date{14 July 1994 \\ Release 1.0.3} % XXX update before release!
|
||||
|
||||
% Tell \index to actually write the .idx file
|
||||
\makeindex
|
||||
|
|
|
|||
|
|
@ -5,7 +5,7 @@ It is not intended as a tutorial.
|
|||
|
||||
While I am trying to be as precise as possible, I chose to use English
|
||||
rather than formal specifications for everything except syntax and
|
||||
lexical analysis. This should make the document better understandable
|
||||
lexical analysis. This should make the document more understandable
|
||||
to the average reader, but will leave room for ambiguities.
|
||||
Consequently, if you were coming from Mars and tried to re-implement
|
||||
Python from this document alone, you might have to guess things and in
|
||||
|
|
|
|||
|
|
@ -354,7 +354,8 @@ meaning:
|
|||
|
||||
\begin{verbatim}
|
||||
( ) [ ] { }
|
||||
; , : . ` =
|
||||
, : . " ` '
|
||||
= ;
|
||||
\end{verbatim}
|
||||
|
||||
The following printing ASCII characters are not used in Python. Their
|
||||
|
|
@ -363,7 +364,7 @@ error:
|
|||
\index{ASCII}
|
||||
|
||||
\begin{verbatim}
|
||||
@ $ " ?
|
||||
@ $ ?
|
||||
\end{verbatim}
|
||||
|
||||
They may be used by future versions of the language though!
|
||||
|
|
|
|||
|
|
@ -9,7 +9,7 @@
|
|||
A {\em code block} is a piece of Python program text that can be
|
||||
executed as a unit, such as a module, a class definition or a function
|
||||
body. Some code blocks (like modules) are executed only once, others
|
||||
(like function bodies) may be executed many times. Code block may
|
||||
(like function bodies) may be executed many times. Code blocks may
|
||||
textually contain other code blocks. Code blocks may invoke other
|
||||
code blocks (that may or may not be textually contained in them) as
|
||||
part of their execution, e.g. by invoking (calling) a function.
|
||||
|
|
@ -72,7 +72,7 @@ When a global name is not found in the global name space, it is
|
|||
searched in the list of ``built-in'' names (which is actually the
|
||||
global name space of the module \verb@__builtin__@). When a name is not
|
||||
found at all, the \verb@NameError@ exception is raised.%
|
||||
\footnote{If the code block contains \verb@exec@ statement or the
|
||||
\footnote{If the code block contains \verb@exec@ statements or the
|
||||
construct \verb@from ... import *@, the semantics of names not
|
||||
explicitly mentioned in a \verb@global@ statement change subtly: name
|
||||
lookup first searches the local name space, then the global one, then
|
||||
|
|
|
|||
|
|
@ -133,7 +133,7 @@ tuples are immutable, the rules for literals apply here.
|
|||
(Note that tuples are not formed by the parentheses, but rather by use
|
||||
of the comma operator. The exception is the empty tuple, for which
|
||||
parentheses {\em are} required --- allowing unparenthesized ``nothing''
|
||||
in expressions would causes ambiguities and allow common typos to
|
||||
in expressions would cause ambiguities and allow common typos to
|
||||
pass uncaught.)
|
||||
\index{comma}
|
||||
\indexii{tuple}{display}
|
||||
|
|
@ -677,7 +677,7 @@ comma-separated values is required.
|
|||
An expression (condition) list containing at least one comma yields a
|
||||
tuple. The length of the tuple is the number of expressions
|
||||
(conditions) in the list. The expressions (conditions) are evaluated
|
||||
from left to right. (Conditions lists are used syntactically is a few
|
||||
from left to right. (Condition lists are used syntactically is a few
|
||||
places where no tuple is constructed but a list of values is needed
|
||||
nevertheless.)
|
||||
\obindex{tuple}
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue