calibre/epydoc.conf
Kovid Goyal 1c8319a5a4 Added working support for the following commands to libprs500:
- ls -lhR --color
 - cp from device to host
 - info  (get device information)
 - cat files on device

Added a command line interface in prs500.py

Added documentation in epytext

Added support for distutils
2006-11-07 04:10:11 +00:00

52 lines
1.5 KiB
Plaintext

[epydoc] # Epydoc section marker (required by ConfigParser)
# Information about the project.
name: libprs500
#url: http://
# The list of modules to document. Modules can be named using
# dotted names, module filenames, or package directory names.
# This option may be repeated.
modules: libprs500, scripts/prs500.py, usb, struct
# Write html output to the directory "apidocs"
output: html
target: docs/html
frames: no
# graph
# The list of graph types that should be automatically included
# in the output. Graphs are generated using the Graphviz "dot"
# executable. Graph types include: "classtree", "callgraph",
# "umlclass". Use "all" to include all graph types
graph: classtree
# css
# The CSS stylesheet for HTML output. Can be the name of a builtin
# stylesheet, or the name of a file.
css: white
# link
# HTML code for the project link in the navigation bar. If left
# unspecified, the project link will be generated based on the
# project's name and URL.
#link: <a href="somewhere">My Cool Project</a>
# top
# The "top" page for the documentation. Can be a URL, the name
# of a module or class, or one of the special names "trees.html",
# "indices.html", or "help.html"
top: libprs500
# verbosity
# An integer indicating how verbose epydoc should be. The default
# value is 0; negative values will supress warnings and errors;
# positive values will give more verbose output.
#verbosity: 0
# separate-classes
# Whether each class should be listed in its own section when
# generating LaTeX or PDF output.
#separate-classes: no