Commit fc167eff authored by Greg Ward's avatar Greg Ward

Changed the table of per-platform default installation locations to be

more consistent with the rest of the Python docs.
parent 7eeadf65
...@@ -249,7 +249,7 @@ Python and extensions) that will be installed. ...@@ -249,7 +249,7 @@ Python and extensions) that will be installed.
In the future, more directories will be added to handle Python scripts, In the future, more directories will be added to handle Python scripts,
documentation, binary executables, and whatever else is needed to handle documentation, binary executables, and whatever else is needed to handle
the job of installing Python modules and applicatins. the job of installing Python modules and applications.
\subsection{How installation works} \subsection{How installation works}
...@@ -266,26 +266,37 @@ the standard location for third-party Python modules. This location ...@@ -266,26 +266,37 @@ the standard location for third-party Python modules. This location
varies by platform and by how you built/installed Python itself. On varies by platform and by how you built/installed Python itself. On
Unix and Mac OS, it also depends on whether the module distribution Unix and Mac OS, it also depends on whether the module distribution
being installed is pure Python or contains extensions (``non-pure''): being installed is pure Python or contains extensions (``non-pure''):
\begin{tableiii}{lll}{textrm}% \begin{tableiv}{l|l|l|c}{textrm}%
{Platform}{Standard installation location}{Default value} {Platform}{Standard installation location}{Default value}{Notes}
\lineiii{Unix (pure Python modules)} \lineiv{Unix (pure)}
{\file{\filevar{prefix}/lib/python1.6/site-packages}} {\filenq{\var{prefix}/lib/python1.6/site-packages}}
{\file{/usr/local/lib/python1.6/site-packages}} {\filenq{/usr/local/lib/python1.6/site-packages}}
\lineiii{Unix (non-pure distribution)} {}
{\file{\filevar{exec-prefix}/lib/python1.6/site-packages}} \lineiv{Unix (non-pure)}
{\file{/usr/local/lib/python1.6/site-packages}} {\filenq{\var{exec-prefix}/lib/python1.6/site-packages}}
\lineiii{Windows} {\filenq{/usr/local/lib/python1.6/site-packages}}
{\filevar{prefix}} {}
{\file{C:\bslash{}Python} \lineiv{Windows}
\footnote{\file{C:\bslash{}Program Files\bslash{}Python} {\filenq{\var{prefix}}}
under Python 1.6a1 and earlier}} {\filenq{C:\bslash{}Python}}
\lineiii{Mac~OS (pure Python modules)} {(1)}
{\file{\filevar{prefix}}:Lib} \lineiv{Mac~OS (pure)}
{\file{Python:Lib}\XXX{???}} {\filenq{\var{prefix}:Lib}}
\lineiii{Mac~OS (non-pure distribution)} {\filenq{Python:Lib} \XXX{???}}
{\file{\filevar{prefix}}:Mac:PlugIns} {}
{\file{Python:Mac:PlugIns}\XXX{???}} \lineiv{Mac~OS (non-pure)}
\end{tableiii} {\var{prefix}:Mac:PlugIns}
{\filenq{Python:Mac:PlugIns}\XXX{???}}
{}
\end{tableiv}
\noindent Notes:
\begin{description}
\item[(1)] The default installation directory on Windows was
\file{C:\bslash{}Program Files\bslash{}Python} under Python 1.6a1,
1.5.2, and earlier.
\end{description}
\filevar{prefix} and \filevar{exec-prefix} stand for the directories \filevar{prefix} and \filevar{exec-prefix} stand for the directories
that Python is installed to, and where it finds its libraries at that Python is installed to, and where it finds its libraries at
run-time. They are always the same under Windows and Mac~OS, and very run-time. They are always the same under Windows and Mac~OS, and very
......
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