mentioned in the \option{packages} list. In order to do this, of

course, there has to be a correspondence between package names and

directories in the filesystem. The default correspondence is the most

\file{distutils} relative to the distribution root. Thus, when you say

\code{packages = ['foo']} in your setup script, you are promising that

the Distutils will find a file \file{foo/\_\_init\_\_.py} (which might

that's no problem: you just have to supply the \option{package\_dir}

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

are in \file{lib/foo}, and so forth. Then you would put

\begin{verbatim}

\code{packages = ['foo']}, you are promising that the file

\file{lib/foo/\_\_init\_\_.py} exists.

would be written in the setup script as

\begin{verbatim}

\end{verbatim}

Note that a \code{\var{package}: \var{dir}} entry in the

\option{package\_dir} option implicitly applies to all packages below

here. In this example, having \code{packages = ['foo', 'foo.bar']}

tells the Distutils to look for \file{lib/\_\_init\_\_.py} and

\file{lib/bar/\_\_init\_\_.py}.

\end{verbatim}

This describes two modules, one of them in the ``root'' package, the

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}

exists as well. And again, you can override the package/directory