From 5896cb8c7aba4477bd9d09fb94a129ee2e8ad11a Mon Sep 17 00:00:00 2001 From: Travis Oliphant Date: Sun, 30 Dec 2007 09:59:39 +0000 Subject: Add a Raises section to the docstring suggestions. --- numpy/doc/HOWTO_DOCUMENT.txt | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) (limited to 'numpy/doc') diff --git a/numpy/doc/HOWTO_DOCUMENT.txt b/numpy/doc/HOWTO_DOCUMENT.txt index 4c32013ee..bb147068d 100644 --- a/numpy/doc/HOWTO_DOCUMENT.txt +++ b/numpy/doc/HOWTO_DOCUMENT.txt @@ -89,7 +89,11 @@ The proposed sections of the docstring are: functions with a large number of keyword argument can still be well documented without cluttering the main parameters' list. -6. **See also:** +6. **Raises:** + An optional section detailing which errors get raised under what + conditions. + +7. **See also:** An optional section used to refer to related code. This section can be very useful, but should be used judiciously. The goal is to direct users to other functions they may not be aware of, or have @@ -97,13 +101,13 @@ The proposed sections of the docstring are: example). Routines whose docstrings further explain parameters used by this function are good candidates. -7. **Notes:** +8. **Notes:** An optional section that provides additional information about the code, possibly including a discussion of the algorithm. This section may include mathematical equations, possibly written in `LaTeX `__. -8. **Examples:** +9. **Examples:** An optional section for examples, using the `doctest `__ format. It can provide an inline mini-tutorial as well as additional -- cgit v1.2.1