Use \shortversion in a number of places.

This partially addresses SourceForge bug #114318.
This commit is contained in:
Fred Drake 2000-09-14 20:24:17 +00:00
parent 3cdb89d5ec
commit d5d0435617
3 changed files with 12 additions and 12 deletions

View file

@ -19,7 +19,7 @@ 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 Macintosh or Windows) or
it uses first \file{lib/python{\var{version}}/site-packages} and then
it uses first \file{lib/python\shortversion/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
@ -39,10 +39,10 @@ refers to a directory (rather than a file). No item is added to
For example, suppose \code{sys.prefix} and \code{sys.exec_prefix} are
set to \file{/usr/local}. The Python \version\ library is then
installed in \file{/usr/local/lib/python\var{version}} (where
\var{version} is the first three characters of \code{sys.version}).
Suppose this has a subdirectory
\file{/usr/local/lib/python\var{version}/site-packages} with three
installed in \file{/usr/local/lib/python\shortversion} (where only the
first three characters of \code{sys.version} are used to form the
installation path name). Suppose this has a subdirectory
\file{/usr/local/lib/python\shortversion/site-packages} with three
subsubdirectories, \file{foo}, \file{bar} and \file{spam}, and two
path configuration files, \file{foo.pth} and \file{bar.pth}. Assume
\file{foo.pth} contains the following: