| 1 | == Documentation == |
| 2 | As per the Python standard, we use [http://epydoc.sourceforge.net/docstrings.html DocStrings] to document each function/class.[[BR]] |
| 3 | These can be queried on the command line: |
| 4 | {{{ |
| 5 | >>> print myfunction.__doc__ |
| 6 | }}} |
| 7 | They are also used by [http://epydoc.sourceforge.net Epydoc] to generate our [http://epydoc.sahanapy.org API documentation]. |
| 8 | |
| 9 | Individual routines inside functions should still have comments to explain them. |
| 10 | |
| 11 | [wiki:InstallationGuidelines User Guides] & [wiki:DeveloperGuidelines Developer Guides] are written on the Wiki.[[BR]] |
| 12 | Trac can be [wiki:BluePrintTrac enhanced] to make it's Wiki more usable, otherwise we may switch to [http://www.dokuwiki.org DokuWiki] for the User Guides. |
| 13 | |
| 14 | To generate a PDF version with low work, we could look to use: |
| 15 | * http://trac-hacks.org/wiki/TracWikiToPdfPlugin |
| 16 | ---- |
| 17 | DeveloperGuidelines |