Continue going through the language reference, bringing it up-to-date.

birkenfeld · birkenfeld · commit 96593ed34807 · 2007-09-07T14:15:41.000Z
In particular, document the new comprehensions and remove mentions of long integers.
Fix a bunch of related things in the lib ref.
diff --git a/Doc/library/constants.rst b/Doc/library/constants.rst
@@ -5,6 +5,11 @@ Built-in Constants
 A small number of constants live in the built-in namespace.  They are:
 
 
+.. note::
+
+   :data:`None`, :data:`False`, :data:`True` and :data:`__debug__` cannot be
+   reassigned, so they can be considered "true" constants.
+
 .. XXX False, True, None are keywords too
 
 .. data:: False
@@ -37,3 +42,10 @@ A small number of constants live in the built-in namespace.  They are:
    slicing syntax for user-defined container data types, as in ::
 
       val = container[1:5, 7:10, ...]
+
+
+.. data:: __debug__
+
+   A boolean value that is :data:`True` if Python was not started with the
+   ``-O`` command line option.  Its value is used indirectly by the
+   :keyword:`assert` statement, but it can also be used directly in code.
diff --git a/Doc/library/fileinput.rst b/Doc/library/fileinput.rst
@@ -19,10 +19,10 @@ The typical use is::
 This iterates over the lines of all files listed in ``sys.argv[1:]``, defaulting
 to ``sys.stdin`` if the list is empty.  If a filename is ``'-'``, it is also
 replaced by ``sys.stdin``.  To specify an alternative list of filenames, pass it
-as the first argument to :func:`input`.  A single file name is also allowed.
+as the first argument to :func:`.input`.  A single file name is also allowed.
 
 All files are opened in text mode by default, but you can override this by
-specifying the *mode* parameter in the call to :func:`input` or
+specifying the *mode* parameter in the call to :func:`.input` or
 :class:`FileInput()`.  If an I/O error occurs during opening or reading a file,
 :exc:`IOError` is raised.
 
diff --git a/Doc/library/new.rst b/Doc/library/new.rst
@@ -50,4 +50,4 @@ The :mod:`new` module defines the following functions:
 
    This function returns a new class object, with name *name*, derived from
    *baseclasses* (which should be a tuple of classes) and with namespace *dict*.
-
+   Alias for the built-in :class:`type`.
diff --git a/Doc/library/readline.rst b/Doc/library/readline.rst
@@ -12,8 +12,8 @@ The :mod:`readline` module defines a number of functions to facilitate
 completion and reading/writing of history files from the Python interpreter.
 This module can be used directly or via the :mod:`rlcompleter` module.  Settings
 made using  this module affect the behaviour of both the interpreter's
-interactive prompt  and the prompts offered by the :func:`raw_input` and
-:func:`input` built-in functions.
+interactive prompt  and the prompts offered by the built-in :func:`input`
+function.
 
 The :mod:`readline` module defines the following functions:
 
diff --git a/Doc/reference/executionmodel.rst b/Doc/reference/executionmodel.rst
@@ -26,25 +26,24 @@ Naming and binding
 Each occurrence of a name in the program text refers to the :dfn:`binding` of
 that name established in the innermost function block containing the use.
 
-.. index:: single: block
+.. index:: block
 
 A :dfn:`block` is a piece of Python program text that is executed as a unit.
 The following are blocks: a module, a function body, and a class definition.
 Each command typed interactively is a block.  A script file (a file given as
 standard input to the interpreter or specified on the interpreter command line
 the first argument) is a code block.  A script command (a command specified on
-the interpreter command line with the '**-c**' option) is a code block.  The string
-argument passed to the built-in functions :func:`eval` and :func:`exec` is a
-code block. The expression read and evaluated by the built-in function
-:func:`input` is a code block.
+the interpreter command line with the '**-c**' option) is a code block.  The
+string argument passed to the built-in functions :func:`eval` and :func:`exec`
+is a code block.
 
 .. index:: pair: execution; frame
 
 A code block is executed in an :dfn:`execution frame`.  A frame contains some
 administrative information (used for debugging) and determines where and how
 execution continues after the code block's execution has completed.
 
-.. index:: single: scope
+.. index:: scope
 
 A :dfn:`scope` defines the visibility of a name within a block.  If a local
 variable is defined in a block, its scope includes that block.  If the
@@ -61,10 +60,11 @@ scope.  The set of all such scopes visible to a code block is called the block's
 
 .. index:: pair: free; variable
 
-If a name is bound in a block, it is a local variable of that block. If a name
-is bound at the module level, it is a global variable.  (The variables of the
-module code block are local and global.)  If a variable is used in a code block
-but not defined there, it is a :dfn:`free variable`.
+If a name is bound in a block, it is a local variable of that block, unless
+declared as :keyword:`nonlocal`.  If a name is bound at the module level, it is
+a global variable.  (The variables of the module code block are local and
+global.)  If a variable is used in a code block but not defined there, it is a
+:dfn:`free variable`.
 
 .. index::
    single: NameError (built-in exception)
@@ -96,18 +96,20 @@ function definition or at the module level (the top-level code block).
 
 If a name binding operation occurs anywhere within a code block, all uses of the
 name within the block are treated as references to the current block.  This can
-lead to errors when a name is used within a block before it is bound. This rule
+lead to errors when a name is used within a block before it is bound.  This rule
 is subtle.  Python lacks declarations and allows name binding operations to
 occur anywhere within a code block.  The local variables of a code block can be
 determined by scanning the entire text of the block for name binding operations.
 
-If the global statement occurs within a block, all uses of the name specified in
-the statement refer to the binding of that name in the top-level namespace.
-Names are resolved in the top-level namespace by searching the global namespace,
-i.e. the namespace of the module containing the code block, and the builtin
-namespace, the namespace of the module :mod:`__builtin__`.  The global namespace
-is searched first.  If the name is not found there, the builtin namespace is
-searched.  The global statement must precede all uses of the name.
+If the :keyword:`global` statement occurs within a block, all uses of the name
+specified in the statement refer to the binding of that name in the top-level
+namespace.  Names are resolved in the top-level namespace by searching the
+global namespace, i.e. the namespace of the module containing the code block,
+and the builtin namespace, the namespace of the module :mod:`__builtin__`.  The
+global namespace is searched first.  If the name is not found there, the builtin
+namespace is searched.  The global statement must precede all uses of the name.
+
+.. XXX document "nonlocal" semantics here
 
 .. index:: pair: restricted; execution
 
@@ -137,7 +139,7 @@ block.  If the nearest enclosing scope for a free variable contains a global
 statement, the free variable is treated as a global.
 
 A class definition is an executable statement that may use and define names.
-These references follow the normal rules for name resolution. The namespace of
+These references follow the normal rules for name resolution.  The namespace of
 the class definition becomes the attribute dictionary of the class.  Names
 defined at the class scope are not visible in methods.
 
@@ -157,13 +159,14 @@ If the wild card form of import --- ``import *`` --- is used in a function and
 the function contains or is a nested block with free variables, the compiler
 will raise a :exc:`SyntaxError`.
 
-The :func:`eval` and :func:`exec` functions do
-not have access to the full environment for resolving names.  Names may be
-resolved in the local and global namespaces of the caller.  Free variables are
-not resolved in the nearest enclosing namespace, but in the global namespace.
-[#]_ The :func:`exec` and :func:`eval` functions have optional
-arguments to override the global and local namespace.  If only one namespace is
-specified, it is used for both.
+.. XXX from * also invalid with relative imports (at least currently)
+
+The :func:`eval` and :func:`exec` functions do not have access to the full
+environment for resolving names.  Names may be resolved in the local and global
+namespaces of the caller.  Free variables are not resolved in the nearest
+enclosing namespace, but in the global namespace.  [#]_ The :func:`exec` and
+:func:`eval` functions have optional arguments to override the global and local
+namespace.  If only one namespace is specified, it is used for both.
 
 
 .. _exceptions:
@@ -205,28 +208,24 @@ re-entering the offending piece of code from the top).
 
 When an exception is not handled at all, the interpreter terminates execution of
 the program, or returns to its interactive main loop.  In either case, it prints
-a stack backtrace, except when the exception is  :exc:`SystemExit`.
+a stack backtrace, except when the exception is :exc:`SystemExit`.
 
 Exceptions are identified by class instances.  The :keyword:`except` clause is
 selected depending on the class of the instance: it must reference the class of
 the instance or a base class thereof.  The instance can be received by the
 handler and can carry additional information about the exceptional condition.
 
-Exceptions can also be identified by strings, in which case the
-:keyword:`except` clause is selected by object identity.  An arbitrary value can
-be raised along with the identifying string which can be passed to the handler.
-
 .. warning::
 
-   Messages to exceptions are not part of the Python API.  Their contents may
-   change from one version of Python to the next without warning and should not be
+   Exception messages are not part of the Python API.  Their contents may change
+   from one version of Python to the next without warning and should not be
    relied on by code which will run under multiple versions of the interpreter.
 
 See also the description of the :keyword:`try` statement in section :ref:`try`
 and :keyword:`raise` statement in section :ref:`raise`.
 
 .. rubric:: Footnotes
 
-.. [#] This limitation occurs because the code that is executed by these operations is
-   not available at the time the module is compiled.
+.. [#] This limitation occurs because the code that is executed by these operations
+       is not available at the time the module is compiled.
 
diff --git a/Doc/reference/expressions.rst b/Doc/reference/expressions.rst
diff --git a/Doc/reference/toplevel_components.rst b/Doc/reference/toplevel_components.rst
