From 933f0c38ef5e1cbc3f9cfb2f8e5870b4731abdc0 Mon Sep 17 00:00:00 2001 From: Fred Drake Date: Thu, 14 Sep 2000 18:12:48 +0000 Subject: Avoid reference to specific versions of Python where possible. This partially addresses SourceForge bug #114318. --- Doc/api/api.tex | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/Doc/api/api.tex b/Doc/api/api.tex index 227698a..9396960 100644 --- a/Doc/api/api.tex +++ b/Doc/api/api.tex @@ -102,7 +102,7 @@ the installation directory specified to the installer. To include the headers, place both directories (if different) on your compiler's search path for includes. Do \emph{not} place the parent directories on the search path and then use -\samp{\#include }; this will break on +\samp{\#include }; this will break on multi-platform builds since the platform independent headers under \envvar{prefix} include the platform specific headers from \envvar{exec_prefix}. @@ -550,14 +550,14 @@ 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/python1.5} (replacing \file{1.5} with the current +\file{lib/python\var{version}} (replacing \var{version} 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/python1.5}. (In fact, this particular path +\file{/usr/local/lib/python\var{version}}. (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}, -- cgit v0.12