Repository and tarball structure

Hi there,

Martijn Faassen recently made some good points in his blog [1] about the structure of
Python packages and release tarballs. The following quote is right in line with what I
suggested earlier for DirectoryStorage:

"""
Some packages conflate the concept of distribution package and Python package. Thus, the
Python modules are just in the top level of the distribution package, which has an
__init__.py.

This is not good if you want your package to be released to the world, or possibly even be
picked up by a Linux distributor. When I download a release tarball of some interesting
Python extension, I expect to be able to unpack it, and not find all the source right
there. No, I expect a nice README.txt, a INSTALL.txt, a setup.py, and perhaps a
testrunner and a doc directory. I don't want to be bothered with lots of files of the
source code itself.
"""

Note again that this doesn't have to have an effect on the import paths of Python modules,
but just the way Python packages and modules are arranged in the repository and release
tarball.

Yours RFC-ly,

Philipp


[1] http://faassen.n--tree.net/blog/view/weblog/2005/10/07/0


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.


-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl