Trac API Documentation

The code is the authoritative source of documentation, and most classes and methods have a corresponding Python "doc string".

View the documentation

Besides the TracBrowser and looking directly at the code, you can also read the generated API documentation, which only shows the public API in a nicely organized and rendered way:

• Trac 1.0dev: ​apiref | ​apidoc HTML | ​apidoc PDF
• Trac 0.12: apiref for ​0.12 | ​0.12.1 | ​0.12.2 | ​0.12.3 | ​0.12.4rc1 | ​0.12-stable
• Trac 0.11: apiref for ​0.11.7

apiref

Full API reference, generated using ​epydoc.
With epydoc, the entirety of the API is covered, but we have less control over the generated output, as it only shows what's present in the source code. The documentation is a bit more "dry" and feels, well, … auto-generated.

apidoc

Semi-automatic API documentation, generated using ​Sphinx.
This contrasts with the above, as in Sphinx we have fine-grained control over the generated documentation and the order in which it appears. We've also written additional explanations and examples not present in the code. Therefore, this documentation "reads" better than the purely auto-generated manual. The downside is that we don't have yet full coverage of the API. (work in progress)

For now, the two sets of documentations are complementary. One day the Sphinx documentation will be complete and sufficient, at which point we'll probably drop the epydoc part (besides, epydoc itself doesn't seem to be maintained anymore).

Note that as Trac 0.11 and 0.12 were not really prepared for being processed, the quality of the generated documentation is all but perfect. It's not that the one for 0.13dev is, but there we're working on it. The 0.12-stable link and the 0.13dev links above should correspond to the latest version of the corresponding branch.

Generating the documentation

Epydoc — make apiref

Once you have installed epydoc, all you need to do is to go to your Trac trunk checkout and do:

$ make apiref

This will generate the epydoc documentation in ./build/doc/epydoc (start with the index.html page).

Note that while installing epydoc with easy_install might work on Linux (not tested), on Windows you should rather download and execute the Windows installer.

Sphinx — make apidoc

Once you have installed sphinx, go to your Trac trunk checkout and do:

$ make apidoc-html

This will generate the Sphinx documentation in ./build/doc/html (start with the index.html page).

You can also generate a PDF document using ​rst2pdf:

$ make apidoc-pdf

This will generate the ./build/doc/pdf/trac_dev.pdf file.

Alternatively you can invoke make apidoc to get both.

Sphinx is a no brainer easy_install sphinx installation, which will get you the appropriate dependencies (docutils and jinja2).

Same goes for easy_install rst2pdf.