Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Commit 370248d

Browse files
committed
Some clarifications to the 'A simple example' section.
1 parent 19c67f8 commit 370248d

1 file changed

Lines changed: 8 additions & 6 deletions

File tree

Doc/dist/dist.tex

Lines changed: 8 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -69,27 +69,29 @@ \subsection{A simple example}
6969
The setup script is usually quite simple, although since it's written in
7070
Python, there are no arbitrary limits to what you can do. If all you
7171
want to do is distribute a module called \module{foo}, contained in a
72-
file \file{foo.py}, then you can get away with as little as this:
72+
file \file{foo.py}, then your setup script can be as little as this:
7373
\begin{verbatim}
7474
from distutils.core import setup
7575
setup (name = "foo",
7676
version = "1.0",
7777
py_modules = ["foo"])
7878
\end{verbatim}
79+
7980
Some observations:
8081
\begin{itemize}
81-
\item all information that you supply to the Distutils is supplied as
82+
\item most information that you supply to the Distutils is supplied as
8283
keyword arguments to the \function{setup()} function
8384
\item those keyword arguments fall into two categories: package
8485
meta-data (name, version number) and information about what's in the
85-
package (list of pure modules, in this case)
86+
package (a list of pure Python modules, in this case)
8687
\item modules are specified by module name, not filename (the same will
8788
hold true for packages and extensions)
8889
\item it's recommended that you supply a little more meta-data, in
8990
particular your name, email address and a URL for the project
9091
\end{itemize}
9192

92-
To create a source distribution for this module, you would run
93+
To create a source distribution for this module, you would create a
94+
setup script, \file{setup.py}, containing the above code, and run:
9395
\begin{verbatim}
9496
python setup.py sdist
9597
\end{verbatim}
@@ -136,8 +138,8 @@ \subsection{A simple example}
136138
``real'' installer. \command{bdist\_wininst} creates a self-extracting
137139
zip file with a minimal user interface, which is enough for small- to
138140
medium-sized module collections. You'll need to have version XXX of
139-
Wise installed on your system for the \command{bdist\_wise} to work;
140-
it's available from \url{http://foo/bar/baz}.)
141+
Wise installed on your system for the \command{bdist\_wise} command to
142+
work; it's available from \url{http://foo/bar/baz}.)
141143

142144
Other \command{bdist} commands exist for other platforms: for example,
143145
\command{bdist\_rpm} for RPM-based Linux systems, (\command{bdist\_deb})

0 commit comments

Comments
 (0)