2010-05-12 23:28:39 +02:00
|
|
|
# HOW TO EDIT THIS FILE:
|
2013-11-22 08:29:22 +01:00
|
|
|
# The "handy ruler" below makes it easier to edit a package description.
|
|
|
|
# Line up the first '|' above the ':' following the base package name, and
|
|
|
|
# the '|' on the right side marks the last column you can put a character in.
|
|
|
|
# You must make exactly 11 lines for the formatting to be correct. It's also
|
|
|
|
# customary to leave one space after the ':' except on otherwise blank lines.
|
2010-05-12 23:28:39 +02:00
|
|
|
|
|
|
|
|-----handy-ruler------------------------------------------------------|
|
|
|
|
epydoc: epydoc (python api documentation tool)
|
2013-11-22 08:29:22 +01:00
|
|
|
epydoc:
|
2010-05-12 23:28:39 +02:00
|
|
|
epydoc: Epydoc is a tool for generating API documentation for Python modules,
|
|
|
|
epydoc: based on their docstrings. For an example of epydoc's output, see
|
|
|
|
epydoc: the API documentation for epydoc itself (html, pdf). A lightweight
|
|
|
|
epydoc: markup language called epytext can be used to format docstrings,
|
|
|
|
epydoc: and to add information about specific fields, such as parameters and
|
|
|
|
epydoc: instance variables. Epydoc also understands docstrings written in
|
|
|
|
epydoc: reStructuredText, Javadoc, and plaintext.
|
2013-11-22 08:29:22 +01:00
|
|
|
epydoc:
|
2010-05-12 23:28:39 +02:00
|
|
|
epydoc: Home page: http://epydoc.sf.net
|