mirrors/cpython
1
0
Fork 0
mirror of https://github.com/python/cpython.git synced 2025-09-29 19:56:59 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 11

Reformatted wide paragraphs.

Browse source
This commit is contained in:
Greg Ward 2000-04-19 22:48:09 +00:00
parent 4eaa3bfed0
commit d5767a5e43
1 changed files with 22 additions and 23 deletions
Download patch file Download diff file Expand all files Collapse all files

43
Doc/dist/dist.tex vendored
View file

@ -9,8 +9,6 @@
\authoraddress{E-mail: \email{gward@python.net}} \authoraddress{E-mail: \email{gward@python.net}}
\begin{document} \begin{document}
\maketitle \maketitle
@ -201,8 +199,8 @@ distributing, and installing modules using the Distutils. The main
purpose of the setup script is to describe your module distribution to purpose of the setup script is to describe your module distribution to
the Distutils, so that the various commands that operate on your modules the Distutils, so that the various commands that operate on your modules
do the right thing. As we saw in section~\ref{sec:simple-example} do the right thing. As we saw in section~\ref{sec:simple-example}
above, the setup script consists mainly of a call to \function{setup()}, and above, the setup script consists mainly of a call to \function{setup()},
all information supplied to the Distutils is suppled as keyword and all information supplied to the Distutils is suppled as keyword
arguments to \function{setup()}. arguments to \function{setup()}.
Here's a slightly more involved example, which we'll follow for the next Here's a slightly more involved example, which we'll follow for the next
@ -305,12 +303,12 @@ slightly more involved example:
py_modules = ['mod1', 'pkg.mod2'] py_modules = ['mod1', 'pkg.mod2']
\end{verbatim} \end{verbatim}
This describes two modules, one of them in the ``root'' package, the This describes two modules, one of them in the ``root'' package, the
other in the \module{pkg} package. Again, the default other in the \module{pkg} package. Again, the default package/directory
package/directory layout implies that these two modules can be found in layout implies that these two modules can be found in \file{mod1.py} and
\file{mod1.py} and \file{pkg/mod2.py}, and that \file{pkg/\_\_init\_\_.py} \file{pkg/mod2.py}, and that \file{pkg/\_\_init\_\_.py} exists as well.
exists as well. And again, you can override the package/directory And again, you can override the package/directory layout using the
layout using the \option{package\_dir} option. \XXX{not sure if this is \option{package\_dir} option. \XXX{not sure if this is actually
actually true---must check!} true---must check!}
\section{Writing the Setup Configuration File} \section{Writing the Setup Configuration File}
@ -356,8 +354,8 @@ default format for the current platform. The default formats are:
\lineii{Unix}{gzipped tar file (\file{.tar.gz})} \lineii{Unix}{gzipped tar file (\file{.tar.gz})}
\lineii{Windows}{zip file} \lineii{Windows}{zip file}
\end{tableii} \end{tableii}
You can specify as many formats as you like using the \longprogramopt{formats} You can specify as many formats as you like using the
option, for example: \longprogramopt{formats} option, for example:
\begin{verbatim} \begin{verbatim}
python setup.py sdist --formats=gztar,zip python setup.py sdist --formats=gztar,zip
\end{verbatim} \end{verbatim}
@ -489,9 +487,10 @@ python setup.py sdist --manifest-only
(\longprogramopt{manifest-only} implies \longprogramopt{force-manifest}.) (\longprogramopt{manifest-only} implies \longprogramopt{force-manifest}.)
If you don't want to use the default file set, you can supply the If you don't want to use the default file set, you can supply the
\longprogramopt{no-defaults} option. If you use \longprogramopt{no-defaults} and \longprogramopt{no-defaults} option. If you use
don't supply a manifest template (or it's empty, or nothing matches the \longprogramopt{no-defaults} and don't supply a manifest template (or
patterns in it), then your source distribution will be empty. it's empty, or nothing matches the patterns in it), then your source
distribution will be empty.
\section{Creating Built Distributions} \section{Creating Built Distributions}
@ -547,9 +546,9 @@ between someone being able to use your extensions or not.
\XXX{filenames are inaccurate here!} \XXX{filenames are inaccurate here!}
The \command{bdist} command has a \longprogramopt{format} option, similar to The \command{bdist} command has a \longprogramopt{format} option,
the \command{sdist} command, that you can use to select which formats to similar to the \command{sdist} command, that you can use to select which
generate: for example, formats to generate: for example,
\begin{verbatim} \begin{verbatim}
python setup.py bdist --format=zip python setup.py bdist --format=zip
\end{verbatim} \end{verbatim}
@ -580,8 +579,8 @@ The available formats for built distributions are:
\end{description} \end{description}
You don't have to use the \command{bdist} command with the You don't have to use the \command{bdist} command with the
\longprogramopt{formats} option; you can also use the command that directly \longprogramopt{formats} option; you can also use the command that
implements the format you're interested in. Many of these directly implements the format you're interested in. Many of these
\command{bdist} ``sub-commands'' actually generate several similar \command{bdist} ``sub-commands'' actually generate several similar
formats; for instance, the \command{bdist\_dumb} command generates all formats; for instance, the \command{bdist\_dumb} command generates all
the ``dumb'' archive formats (\code{tar}, \code{ztar}, \code{gztar}, and the ``dumb'' archive formats (\code{tar}, \code{ztar}, \code{gztar}, and
@ -676,8 +675,8 @@ anything except backslash or colon; on Mac OS anything except colon.
\XXX{Windows and Mac OS support not there yet} \XXX{Windows and Mac OS support not there yet}
\subsection{Creating a ``built'' distribution: the \protect\command{bdist} command \subsection{Creating a ``built'' distribution: the
family} \protect\command{bdist} command family}
\label{sec:bdist-cmds} \label{sec:bdist-cmds}