Don't assume that \version expands to the 3-character major.minor number; it

is the full release version name ("1.5.1beta1", for instance).

1 files changed, 2 insertions, 2 deletions

diff --git a/Doc/api/api.tex b/Doc/api/api.tex
index e0c3ad2..5b87fd6 100644
--- a/Doc/api/api.tex
+++ b/Doc/api/api.tex
@@ -509,14 +509,14 @@ calculates the module search path based upon its best guess for the
 location of the standard Python interpreter executable, assuming that
 the Python library is found in a fixed location relative to the Python
 interpreter executable.  In particular, it looks for a directory named
-\file{lib/python\version} (replacing \file{\version} with the current
+\file{lib/python1.5} (replacing \file{1.5} with the current
 interpreter version) relative to the parent directory where the
 executable named \file{python} is found on the shell command search
 path (the environment variable \envvar{PATH}).
 
 For instance, if the Python executable is found in
 \file{/usr/local/bin/python}, it will assume that the libraries are in
-\file{/usr/local/lib/python\version}.  (In fact, this particular path
+\file{/usr/local/lib/python1.5}.  (In fact, this particular path
 is also the ``fallback'' location, used when no executable file named
 \file{python} is found along \envvar{PATH}.)  The user can override
 this behavior by setting the environment variable \envvar{PYTHONHOME},