Fix a few doc errors, mostly undefined keywords.

This commit is contained in:
Georg Brandl 2011-01-15 17:03:02 +00:00
parent 6dc50f34dd
commit 375aec2315
14 changed files with 57 additions and 57 deletions

View file

@ -678,7 +678,7 @@ Once the name of the module is known (unless otherwise specified, the term
for the module or package can begin. The first place checked is
:data:`sys.modules`, the cache of all modules that have been imported
previously. If the module is found there then it is used in step (2) of import
unless :keyword:`None` is found in :data:`sys.modules`, in which case
unless ``None`` is found in :data:`sys.modules`, in which case
:exc:`ImportError` is raised.
.. index::
@ -696,7 +696,7 @@ within a package (as denoted by the existence of a dot in the name), then a
second argument to :meth:`find_module` is given as the value of the
:attr:`__path__` attribute from the parent package (everything up to the last
dot in the name of the module being imported). If a finder can find the module
it returns a :term:`loader` (discussed later) or returns :keyword:`None`.
it returns a :term:`loader` (discussed later) or returns ``None``.
.. index::
single: sys.path_hooks
@ -723,11 +723,11 @@ finder cached then :data:`sys.path_hooks` is searched by calling each object in
the list with a single argument of the path, returning a finder or raises
:exc:`ImportError`. If a finder is returned then it is cached in
:data:`sys.path_importer_cache` and then used for that path entry. If no finder
can be found but the path exists then a value of :keyword:`None` is
can be found but the path exists then a value of ``None`` is
stored in :data:`sys.path_importer_cache` to signify that an implicit,
file-based finder that handles modules stored as individual files should be
used for that path. If the path does not exist then a finder which always
returns :keyword:`None` is placed in the cache for the path.
returns ``None`` is placed in the cache for the path.
.. index::
single: loader