them. Let's go with "TowelStuff" since it seems appropriate and also
it has not yet been used on the :ref:`pypi_info`.
Arranging your file and directory structure
Here's what you should do for each of those listed above:
* Put into ``bin`` any scripts you've written that use your
``towelstuff`` package and which you think would be useful for your
users. If you don't have any, then remove the ``bin`` directory.
* For now, the ``CHANGES.txt`` file should only contain::
v<version>, <date> -- Initial release.
since this is your very first version (version number will be
described below) and there are no changes to report.
* The ``docs`` dir should contain any design docs, implementation notes, a
FAQ, or any other docs you've written. For now, stick to plain text
files ending in ".txt". This author (JohnMG) likes to use `Pandoc's
Markdown <http://johnmacfarlane.net/pandoc/>`_, but many Pythoneers
use :term:`reStructuredText <reStructuredText>`.
* The ``LICENSE.txt`` file is often just a copy/paste of your license
of choice. We recommend going with a commonly-used license, such as
* The ``MANIFEST.in`` file should contain this::
recursive-include docs *.txt
* The ``README.txt`` file should be written in :term:`reST <reStructuredText>`
so that the PyPI can use it to generate your project's PyPI page. Here's a
10-second intro to reST that you might use to start with::
html, see the `TowelStuff project
<http://pypi.python.org/pypi/TowelStuff/>`_ at the PyPI.
* ``setup.py`` -- Create this file and make it look like this::
from distutils.core import setup
If you have no scripts to distribute (and thus no ``bin`` dir), you
can remove the above line which begins with "scripts".
* Inside the ``towelstuff`` directory, ``__init__.py`` can be
empty. Likewise, inside ``towelstuff/test``, *that* ``__init__.py``
can be empty as well. If you have no tests written yet, you can