When documentation grows too large it is nice to have clear examples
that stand out of text. Explanation is important to get the idea, but 
for a reference cookbook examples work better.

Here is a patch to clarify the usage of *requires* and *provides*
keywords in setup.py on the documentation page
http://docs.python.org/distutils/setupscript.html#relationships-between-distributions-and-packages


--- setupscript_old.txt	Wed Feb 25 17:09:41 2009
+++ setupscript.txt	Wed Feb 25 17:34:00 2009
@@ -423,6 +423,14 @@
 distribution being described.  If no qualifiers are given, all versions
of the
 named module or package are understood to be obsoleted.
 
+Example of using *requires* and *provides* keywords ::
+
+   setup(...,
+         requires=['dbm', 'foo=>1.1.0'],
+         provides=['myapi (1.1)'],
+        )
+
+
 
 Installing Scripts
 ==================

Another thing for setupscript is to state that long_description is
actually ReStructured text.

> Another thing for setupscript is to state that long_description is
> actually ReStructured text.

I can be free text. If it's ReStructured text it will be parsed by PyPI
but this is it;

For the requires and provides, I am afraid no one really uses theses
option, and they might get deprecated at some point. So I don't think it
worth adding an example for it

I have added more details in r70007. Thanks!

notice that setupscript mentions that long_description is rest:

"""
‘long string’
    Multiple lines of plain text in reStructuredText format (see
http://docutils.sf.net/).
"""