4 # The list of objects to document. Objects can be named using
5 # dotted names, module filenames, or package directory names.
6 # Alases for this option include "objects" and "values".
10 # The type of output that should be generated. Should be one
11 # of: html, text, latex, dvi, ps, pdf.
15 # The path to the output directory. May be relative or absolute.
19 # The default markup language for docstrings, for modules that do
20 # not define __docformat__. Defaults to epytext.
24 # The CSS stylesheet for HTML output. Can be the name of a builtin
25 # stylesheet, or the name of a file.
29 # The documented project's name.
33 # The documented project's URL.
34 url: http://leela.xangell.com:3000/enkel
38 # Whether or not to include a frames-based table of contents.
42 # Whether or not to inclue private variables. (Even if included,
43 # private variables will be hidden by default.)
47 # Whether or not to list each module's imports.
51 # An integer indicating how verbose epydoc should be. The default
52 # value is 0; negative values will supress warnings and errors;
53 # positive values will give more verbose output.
57 # Whether or not parsing should be used to examine objects.
61 # Whether or not introspection should be used to examine objects.
65 # The list of graph types that should be automatically included
66 # in the output. Graphs are generated using the Graphviz "dot"
67 # executable. Graph types include: "classtree", "callgraph",
68 # "umlclass". Use "all" to include all graph types
72 # The path to the Graphviz "dot" executable, used to generate
77 # Whether or not to include syntax highlighted source code in
78 # the output (HTML only).
82 # The name of one or more pstat files (generated by the profile
83 # or hotshot module). These are used to generate call graphs.
87 # Whether each class should be listed in its own section when
88 # generating LaTeX or PDF output.