The py-lib contains some scripts, most of which are small ones (apart from py.test) that help during the python development process. If working from a svn-checkout of py lib you may add py/bin to your shell PATH which should make the scripts available on your command prompt.
The py.test executable is the main entry point into the py-lib testing tool, see the py.test documentation.
Usage: py.cleanup [PATH]
Delete pyc file recursively, starting from PATH (which defaults to the current working directory). Don't follow links and don't recurse into directories with a ".".
Usage: py.countloc [PATHS]
Count (non-empty) lines of python code and number of python files recursively starting from a PATHS given on the command line (starting from the current working directory). Distinguish between test files and normal ones and report them separately.
Usage: py.lookup SEARCH_STRING [options]
Looks recursively at Python files for a SEARCH_STRING, starting from the present working directory. Prints the line, with the filename and line-number prepended.
Usage: py.rest [PATHS] [options]
Loot recursively for .txt files starting from PATHS and convert them to html using docutils (or to pdf files, if the --pdf option is used).
py.rest has some extra features over rst2html (which is shipped with docutils). Most of these are still experimental, the one which is most likely not going to change is the graphviz directive. With that you can embed .dot files into your document and have them be converted to png (when outputting html) and to eps (when outputting pdf). Otherwise the directive works mostly like the image directive:
.. graphviz:: example.dot :scale: 90