1 |
jan |
2345 |
$Id$ |
2 |
|
|
|
3 |
|
|
Currently, there is no explicit document on the implementation |
4 |
|
|
details. But you can generate class and method description |
5 |
|
|
automatically from the source code: |
6 |
|
|
|
7 |
|
|
pydoc coming with Python can be quite useful as a class browser. |
8 |
|
|
If you want to use it on Thuban, you need to give it the right |
9 |
|
|
paths so you can browse all of it. |
10 |
|
|
|
11 |
|
|
e.g. , the following starts pydoc as webbrowser on localhost:1234/ |
12 |
|
|
cd thuban |
13 |
|
|
PYTHONPATH=./Lib:./test/ pydoc -p 1234 |
14 |
|
|
|
15 |
|
|
A brief look into other documentation tools |
16 |
|
|
resulted in that the the best overview about them was coming with |
17 |
|
|
epydoc at: |
18 |
|
|
http://epydoc.sourceforge.net/relatedprojects.html |
19 |
|
|
|
20 |
|
|
epydoc seems to be very solid, because the author did a lot |
21 |
|
|
of reseach and decided for a very simple markup language. |
22 |
|
|
It might be surpased one day by docutils which use the more |
23 |
|
|
complicated reStructured text as markup. |
24 |
|
|
|
25 |
|
|
As nice side contender is happydoc, because it does not import |
26 |
|
|
the python modules. |