[Python-checkins] CVS: python/dist/src/Doc/inst inst.tex,1.15,1.16

2000年6月29日 20:36:44 -0700

Update of /cvsroot/python/python/dist/src/Doc/inst
In directory slayer.i.sourceforge.net:/tmp/cvs-serv19140/inst
Modified Files:
	inst.tex 
Log Message:
Update Python version numbers from 1.6 to 2.0 where appropriate.
Make some references between the distutils documents hyperlinks using
the \citetitle markup.
Index: inst.tex
===================================================================
RCS file: /cvsroot/python/python/dist/src/Doc/inst/inst.tex,v
retrieving revision 1.15
retrieving revision 1.16
diff -C2 -r1.15 -r1.16
*** inst.tex	2000年06月24日 01:33:16	1.15
--- inst.tex	2000年06月30日 03:36:41	1.16
***************
*** 49,53 ****
 In the past, there has been little support for adding third-party
 modules to an existing Python installation. With the introduction of
! the Python Distribution Utilities (Distutils for short) in Python 1.6,
 this is starting to change. Not everything will change overnight,
 though, so while this document concentrates on installing module
--- 49,53 ----
 In the past, there has been little support for adding third-party
 modules to an existing Python installation. With the introduction of
! the Python Distribution Utilities (Distutils for short) in Python 2.0,
 this is starting to change. Not everything will change overnight,
 though, so while this document concentrates on installing module
***************
*** 63,67 ****
 installation, but that's it. If you're looking for information on how
 to distribute your own Python modules so that others may use them, see
! the ``Distributing Python Modules'' manual.
 
 
--- 63,67 ----
 installation, but that's it. If you're looking for information on how
 to distribute your own Python modules so that others may use them, see
! the \citetitle[../dist/dist.html]{Distributing Python Modules} manual.
 
 
***************
*** 275,284 ****
 {Platform}{Standard installation location}{Default value}{Notes}
 \lineiv{Unix (pure)}
! {\filenq{\filevar{prefix}/lib/python1.6/site-packages}}
! {\filenq{/usr/local/lib/python1.6/site-packages}}
 {(1)}
 \lineiv{Unix (non-pure)}
! {\filenq{\filevar{exec-prefix}/lib/python1.6/site-packages}}
! {\filenq{/usr/local/lib/python1.6/site-packages}}
 {(1)}
 \lineiv{Windows}
--- 275,284 ----
 {Platform}{Standard installation location}{Default value}{Notes}
 \lineiv{Unix (pure)}
! {\filenq{\filevar{prefix}/lib/python2.0/site-packages}}
! {\filenq{/usr/local/lib/python2.0/site-packages}}
 {(1)}
 \lineiv{Unix (non-pure)}
! {\filenq{\filevar{exec-prefix}/lib/python2.0/site-packages}}
! {\filenq{/usr/local/lib/python2.0/site-packages}}
 {(1)}
 \lineiv{Windows}
***************
*** 315,323 ****
 running Python in interactive mode and typing a few simple commands.
 Under Unix, just type \code{python} at the shell prompt; under Windows,
! run ``Python 1.6 (interpreter)'' \XXX{right?}; under Mac~OS, \XXX{???}.
! Once the interpreter is started, you type Python code at the \code{>>>}
! prompt. For example, on my Linux system, I type the three Python
! statements shown below, and get the output as shown, to find out my
! \filevar{prefix} and \filevar{exec-prefix}:
 \begin{verbatim}
 Python 1.5.2 (#1, Apr 18 1999, 16:03:16) [GCC pgcc-2.91.60 19981201 (egcs-1.1.1 on linux2
--- 315,324 ----
 running Python in interactive mode and typing a few simple commands.
 Under Unix, just type \code{python} at the shell prompt; under Windows,
! run ``Python 2.0 (interpreter)'' \XXX{right?}; under Mac~OS, \XXX{???}.
! Once the interpreter is started, you type Python code at the
! \samp{>>> } prompt. For example, on my Linux system, I type the three
! Python statements shown below, and get the output as shown, to find
! out my \filevar{prefix} and \filevar{exec-prefix}:
! 
 \begin{verbatim}
 Python 1.5.2 (#1, Apr 18 1999, 16:03:16) [GCC pgcc-2.91.60 19981201 (egcs-1.1.1 on linux2