[Python-checkins] CVS: distutils/doc/dist dist.tex,1.6,1.7

[Greg Ward]

Update of /projects/cvsroot/distutils/doc/dist
In directory kaluha:/tmp/cvs-serv13166

Modified Files:
	dist.tex 
Log Message:
Changed '\package' to \module'.

Index: dist.tex
===================================================================
RCS file: /projects/cvsroot/distutils/doc/dist/dist.tex,v
retrieving revision 1.6
retrieving revision 1.7
diff -C2 -r1.6 -r1.7
*** dist.tex	2000/04/19 22:34:11	1.6
--- dist.tex	2000/04/19 22:36:24	1.7
***************
*** 255,259 ****
  course, there has to be a correspondence between package names and
  directories in the filesystem.  The default correspondence is the most
! obvious one, i.e. package \package{distutils} is found in the directory
  \file{distutils} relative to the distribution root.  Thus, when you say
  \code{packages = ['foo']} in your setup script, you are promising that
--- 255,259 ----
  course, there has to be a correspondence between package names and
  directories in the filesystem.  The default correspondence is the most
! obvious one, i.e. package \module{distutils} is found in the directory
  \file{distutils} relative to the distribution root.  Thus, when you say
  \code{packages = ['foo']} in your setup script, you are promising that
***************
*** 268,272 ****
  option to tell the Distutils about your convention.  For example, say
  you keep all Python source under \file{lib}, so that modules not in any
! package are right in \file{lib}, modules in the \package{foo} package
  are in \file{lib/foo}, and so forth.  Then you would put
  \begin{verbatim}
--- 268,272 ----
  option to tell the Distutils about your convention.  For example, say
  you keep all Python source under \file{lib}, so that modules not in any
! package are right in \file{lib}, modules in the \module{foo} package
  are in \file{lib/foo}, and so forth.  Then you would put
  \begin{verbatim}
***************
*** 280,285 ****
  \file{lib/foo/\_\_init\_\_.py} exists.
  
! Another possible convention is to put the \package{foo} package right in 
! \file{lib}, the \package{foo.bar} package in \file{lib/bar}, etc.  This
  would be written in the setup script as
  \begin{verbatim}
--- 280,285 ----
  \file{lib/foo/\_\_init\_\_.py} exists.
  
! Another possible convention is to put the \module{foo} package right in 
! \file{lib}, the \module{foo.bar} package in \file{lib/bar}, etc.  This
  would be written in the setup script as
  \begin{verbatim}
***************
*** 288,292 ****
  Note that a \code{\var{package}: \var{dir}} entry in the
  \option{package\_dir} option implicitly applies to all packages below
! \var{package}, so the \package{foo.bar} case is automatically handled
  here.  In this example, having \code{packages = ['foo', 'foo.bar']}
  tells the Distutils to look for \file{lib/\_\_init\_\_.py} and
--- 288,292 ----
  Note that a \code{\var{package}: \var{dir}} entry in the
  \option{package\_dir} option implicitly applies to all packages below
! \var{package}, so the \module{foo.bar} case is automatically handled
  here.  In this example, having \code{packages = ['foo', 'foo.bar']}
  tells the Distutils to look for \file{lib/\_\_init\_\_.py} and
***************
*** 306,310 ****
  \end{verbatim}
  This describes two modules, one of them in the ``root'' package, the
! other in the \package{pkg} package.  Again, the default
  package/directory layout implies that these two modules can be found in
  \file{mod1.py} and \file{pkg/mod2.py}, and that \file{pkg/\_\_init\_\_.py}
--- 306,310 ----
  \end{verbatim}
  This describes two modules, one of them in the ``root'' package, the
! other in the \module{pkg} package.  Again, the default
  package/directory layout implies that these two modules can be found in
  \file{mod1.py} and \file{pkg/mod2.py}, and that \file{pkg/\_\_init\_\_.py}