Commit ae2d657d authored by Fred Drake's avatar Fred Drake

Some logical markup.

parent 55cbbfed
......@@ -15,8 +15,8 @@ This will append site-specific paths to to the module search path.
It starts by constructing up to four directories from a head and a
tail part. For the head part, it uses \code{sys.prefix} and
\code{sys.exec_prefix}; empty heads are skipped. For
the tail part, it uses the empty string (on Mac or Windows) or it uses
first \file{lib/python\var{version}/site-packages} and then
the tail part, it uses the empty string (on Macintosh or Windows) or
it uses first \file{lib/python\var{version}/site-packages} and then
\file{lib/site-python} (on \UNIX{}). For each of the distinct
head-tail combinations, it sees if it refers to an existing directory,
and if so, adds to \code{sys.path}, and also inspected for path
......@@ -73,11 +73,11 @@ Note that \file{bletch} is omitted because it doesn't exist; the
configuration file.
After these path manipulations, an attempt is made to import a module
named \code{sitecustomize}\refmodindex{sitecustomize}, which can
named \module{sitecustomize}\refmodindex{sitecustomize}, which can
perform arbitrary site-specific customizations. If this import fails
with an \code{ImportError} exception, it is silently ignored.
with an \exception{ImportError} exception, it is silently ignored.
Note that for some non-\UNIX{} systems, \code{sys.prefix} and
\code{sys.exec_prefix} are empty, and the path manipulations are
skipped; however the import of
\code{sitecustomize}\refmodindex{sitecustomize} is still attempted.
\module{sitecustomize}\refmodindex{sitecustomize} is still attempted.
......@@ -15,8 +15,8 @@ This will append site-specific paths to to the module search path.
It starts by constructing up to four directories from a head and a
tail part. For the head part, it uses \code{sys.prefix} and
\code{sys.exec_prefix}; empty heads are skipped. For
the tail part, it uses the empty string (on Mac or Windows) or it uses
first \file{lib/python\var{version}/site-packages} and then
the tail part, it uses the empty string (on Macintosh or Windows) or
it uses first \file{lib/python\var{version}/site-packages} and then
\file{lib/site-python} (on \UNIX{}). For each of the distinct
head-tail combinations, it sees if it refers to an existing directory,
and if so, adds to \code{sys.path}, and also inspected for path
......@@ -73,11 +73,11 @@ Note that \file{bletch} is omitted because it doesn't exist; the
configuration file.
After these path manipulations, an attempt is made to import a module
named \code{sitecustomize}\refmodindex{sitecustomize}, which can
named \module{sitecustomize}\refmodindex{sitecustomize}, which can
perform arbitrary site-specific customizations. If this import fails
with an \code{ImportError} exception, it is silently ignored.
with an \exception{ImportError} exception, it is silently ignored.
Note that for some non-\UNIX{} systems, \code{sys.prefix} and
\code{sys.exec_prefix} are empty, and the path manipulations are
skipped; however the import of
\code{sitecustomize}\refmodindex{sitecustomize} is still attempted.
\module{sitecustomize}\refmodindex{sitecustomize} is still attempted.
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment