[Python-checkins] CVS: python/dist/src/Doc/inst inst.tex,1.35,1.36
Fred L. Drake
fdrake@users.sourceforge.net
2001年9月25日 08:12:43 -0700
Update of /cvsroot/python/python/dist/src/Doc/inst
In directory usw-pr-cvs1:/tmp/cvs-serv26572/inst
Modified Files:
inst.tex
Log Message:
Fix a URL (closing SF patch #462195).
Cleaned up a bunch of XXX comments containing links to additional
information, replacing them with proper references.
Replaced "MacOS" with "Mac OS", since that's what the style guide says.
Index: inst.tex
===================================================================
RCS file: /cvsroot/python/python/dist/src/Doc/inst/inst.tex,v
retrieving revision 1.35
retrieving revision 1.36
diff -C2 -d -r1.35 -r1.36
*** inst.tex 2001年09月11日 15:10:42 1.35
--- inst.tex 2001年09月25日 15:12:41 1.36
***************
*** 148,152 ****
find them. This document makes no such assumptions, and explains how
the Python library is laid out on three major platforms (\UNIX, Windows,
! and MacOS), so that you can understand what happens when the Distutils
do their job \emph{and} know how to install modules manually when the
module author fails to provide a setup script.
--- 148,152 ----
find them. This document makes no such assumptions, and explains how
the Python library is laid out on three major platforms (\UNIX, Windows,
! and Mac OS), so that you can understand what happens when the Distutils
do their job \emph{and} know how to install modules manually when the
module author fails to provide a setup script.
***************
*** 178,182 ****
On \UNIX, you'd run this command from a shell prompt; on Windows, you
have to open a command prompt window (``DOS box'') and do it there; on
! MacOS, things are a tad more complicated (see below).
--- 178,182 ----
On \UNIX, you'd run this command from a shell prompt; on Windows, you
have to open a command prompt window (``DOS box'') and do it there; on
! Mac OS, things are a tad more complicated (see below).
***************
*** 209,213 ****
\end{verbatim}
! On MacOS, you have to go through a bit more effort to supply
command-line arguments to the setup script:
\begin{itemize}
--- 209,213 ----
\end{verbatim}
! On Mac OS, you have to go through a bit more effort to supply
command-line arguments to the setup script:
\begin{itemize}
***************
*** 318,322 ****
the standard location for third-party Python modules. This location
varies by platform and by how you built/installed Python itself. On
! \UNIX{} and MacOS, it also depends on whether the module distribution
being installed is pure Python or contains extensions (``non-pure''):
\begin{tableiv}{l|l|l|c}{textrm}%
--- 318,322 ----
the standard location for third-party Python modules. This location
varies by platform and by how you built/installed Python itself. On
! \UNIX{} and Mac OS, it also depends on whether the module distribution
being installed is pure Python or contains extensions (``non-pure''):
\begin{tableiv}{l|l|l|c}{textrm}%
***************
*** 334,342 ****
{\filenq{C:\textbackslash{}Python}}
{(2)}
! \lineiv{MacOS (pure)}
{\filenq{\filevar{prefix}:Lib:site-packages}}
{\filenq{Python:Lib:site-packages}}
{}
! \lineiv{MacOS (non-pure)}
{\filenq{\filevar{prefix}:Lib:site-packages}}
{\filenq{Python:Lib:site-packages}}
--- 334,342 ----
{\filenq{C:\textbackslash{}Python}}
{(2)}
! \lineiv{Mac OS (pure)}
{\filenq{\filevar{prefix}:Lib:site-packages}}
{\filenq{Python:Lib:site-packages}}
{}
! \lineiv{Mac OS (non-pure)}
{\filenq{\filevar{prefix}:Lib:site-packages}}
{\filenq{Python:Lib:site-packages}}
***************
*** 358,362 ****
\filevar{prefix} and \filevar{exec-prefix} stand for the directories
that Python is installed to, and where it finds its libraries at
! run-time. They are always the same under Windows and MacOS, and very
often the same under \UNIX. You can find out what your Python
installation uses for \filevar{prefix} and \filevar{exec-prefix} by
--- 358,362 ----
\filevar{prefix} and \filevar{exec-prefix} stand for the directories
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
often the same under \UNIX. You can find out what your Python
installation uses for \filevar{prefix} and \filevar{exec-prefix} by
***************
*** 364,368 ****
Under \UNIX, just type \code{python} at the shell prompt. Under
Windows, choose \menuselection{Start \sub Programs \sub Python
! 2.1 \sub Python (command line)}. Under MacOS, \XXX{???}.
Once the interpreter is started, you type Python code at the
prompt. For example, on my Linux system, I type the three Python
--- 364,368 ----
Under \UNIX, just type \code{python} at the shell prompt. Under
Windows, choose \menuselection{Start \sub Programs \sub Python
! 2.1 \sub Python (command line)}. Under Mac OS, \XXX{???}.
Once the interpreter is started, you type Python code at the
prompt. For example, on my Linux system, I type the three Python
***************
*** 436,441 ****
This subsection describes the necessary steps to use Distutils with the
! Borland \Cpp{} compiler version 5.5.\footnote{Check
! \url{http://www.borland.com/bcppbuilder/freecompiler/} for download}
%Should we mention that users have to create cfg-files for the compiler
%see also http://community.borland.com/article/0,1410,21205,00.html
--- 436,440 ----
This subsection describes the necessary steps to use Distutils with the
! Borland \Cpp{} compiler version 5.5.
%Should we mention that users have to create cfg-files for the compiler
%see also http://community.borland.com/article/0,1410,21205,00.html
***************
*** 479,485 ****
file for Distutils (see section~\ref{config-files}.)
! \XXX{One place to look: \url{http://www.cyberus.ca/~g_will/pyExtenDL.shtml}}
\subsubsection{GNU C / Cygwin / MinGW32}
--- 478,494 ----
file for Distutils (see section~\ref{config-files}.)
! \begin{seealso}
! \seetitle[http://www.borland.com/bcppbuilder/freecompiler/]
! {\Cpp{}Builder Compiler}
! {Information about the free \Cpp{} compiler from Borland,
! including links to the download pages.}
+ \seetitle[http://www.cyberus.ca/~g_will/pyExtenDL.shtml]
+ {Creating Python Extensions Using Borland's Free Compiler}
+ {Document describing how to use Borland's free command-line C++
+ compiler to build Python.}
+ \end{seealso}
+
\subsubsection{GNU C / Cygwin / MinGW32}
***************
*** 488,492 ****
distributions.\footnote{Check
\url{http://sources.redhat.com/cygwin/} and
! \url{http://www.mingw.org} for more information}
\XXX{For a Python which was built with Cygwin, all should work without
--- 497,501 ----
distributions.\footnote{Check
\url{http://sources.redhat.com/cygwin/} and
! \url{http://www.mingw.org/} for more information}
\XXX{For a Python which was built with Cygwin, all should work without
***************
*** 512,515 ****
--- 521,525 ----
dlltool --dllname python20.dll --def python20.def --output-lib libpython20.a
\end{verbatim}
+
The resulting library has to be placed in the same directory as
\file{python20.lib}. (Should be the \file{libs} directory under your
***************
*** 527,532 ****
\end{verbatim}
! and for Cygwin in no-cygwin mode\footnote{Then you have no POSIX emulation
! available, but you also don't need \file{cygwin1.dll}.} or for MinGW32 type
\begin{verbatim}
--- 537,543 ----
\end{verbatim}
! and for Cygwin in no-cygwin mode\footnote{Then you have no
! \POSIX{} emulation available, but you also don't need
! \file{cygwin1.dll}.} or for MinGW32 type:
\begin{verbatim}
***************
*** 538,545 ****
for Distutils (see section~\ref{config-files}.)
! \XXX{One place to look: \url{http://www.zope.org/Members/als/tips/win32_mingw_modules}}
! \XXX{For converted import libraries in cygwin/mingw32 and bcpp format,
! see \url{ftp://pyopengl.sourceforge.net/pub/pyopengl/win32-stuff/}.}
--- 549,563 ----
for Distutils (see section~\ref{config-files}.)
! \begin{seealso}
! \seetitle[http://www.zope.org/Members/als/tips/win32_mingw_modules]
! {Building Python modules on MS Windows platform with MinGW32}
! {Information about building the required libraries for the MinGW32
! environment.}
! \seeurl{http://pyopengl.sourceforge.net/ftp/win32-stuff/}
! {Converted import libraries in Cygwin/MinGW32 and Borland format,
! and a script to create the registry entries needed for Distutils
! to locate the built Python.}
! \end{seealso}
***************
*** 570,574 ****
Under \UNIX, there are two ways to perform an alternate installation.
The ``prefix scheme'' is similar to how alternate installation works
! under Windows and MacOS, but is not necessarily the most useful way to
maintain a personal Python library. Hence, we document the more
convenient and commonly useful ``home scheme'' first.
--- 588,592 ----
Under \UNIX, there are two ways to perform an alternate installation.
The ``prefix scheme'' is similar to how alternate installation works
! under Windows and Mac OS, but is not necessarily the most useful way to
maintain a personal Python library. Hence, we document the more
convenient and commonly useful ``home scheme'' first.
***************
*** 697,704 ****
! \subsection{Alternate installation: MacOS}
\label{alt-install-macos}
! Like Windows, MacOS has no notion of home directories (or even of
users), and a fairly simple standard Python installation. Thus, only a
\longprogramopt{prefix} option is needed. It defines the installation
--- 715,722 ----
! \subsection{Alternate installation: Mac OS}
\label{alt-install-macos}
! Like Windows, Mac OS has no notion of home directories (or even of
users), and a fairly simple standard Python installation. Thus, only a
\longprogramopt{prefix} option is needed. It defines the installation
***************
*** 773,777 ****
Of course, you also have to ensure that these directories are in
Python's module search path, e.g. by putting a \file{.pth} file in
! \filevar{prefix} (\XXX{should have a section describing .pth files and
cross-ref it here}).
--- 791,795 ----
Of course, you also have to ensure that these directories are in
Python's module search path, e.g. by putting a \file{.pth} file in
! \filevar{prefix} (\XXX{should have a section describing \file{.pth} files and
cross-ref it here}).
***************
*** 853,860 ****
\code{\$PLAT}. (And of course, you can only use the configuration
variables supplied by the Distutils on systems that don't have
! environment variables, such as MacOS (\XXX{true?}).) See
section~\ref{config-files} for details.
! \XXX{need some Windows and MacOS examples---when would custom
installation schemes be needed on those platforms?}
--- 871,878 ----
\code{\$PLAT}. (And of course, you can only use the configuration
variables supplied by the Distutils on systems that don't have
! environment variables, such as Mac OS (\XXX{true?}).) See
section~\ref{config-files} for details.
! \XXX{need some Windows and Mac OS examples---when would custom
installation schemes be needed on those platforms?}
***************
*** 894,898 ****
\end{tableiii}
! And on MacOS, they are:
\begin{tableiii}{l|l|c}{textrm}
{Type of file}{Location and filename}{Notes}
--- 912,916 ----
\end{tableiii}
! And on Mac OS, they are:
\begin{tableiii}{l|l|c}{textrm}
{Type of file}{Location and filename}{Notes}
***************
*** 933,937 ****
prefix is just \file{Python:}, so under Python 1.6 and later this is
normally\file{Python:Lib:distutils:pydistutils.cfg}. (The Distutils
! don't work very well with Python 1.5.2 under MacOS. \XXX{true?})
\end{description}
--- 951,955 ----
prefix is just \file{Python:}, so under Python 1.6 and later this is
normally\file{Python:Lib:distutils:pydistutils.cfg}. (The Distutils
! don't work very well with Python 1.5.2 under Mac OS. \XXX{true?})
\end{description}