summaryrefslogtreecommitdiff
path: root/doc/ext
diff options
context:
space:
mode:
authorGeorg Brandl <georg@python.org>2009-01-22 19:22:49 +0100
committerGeorg Brandl <georg@python.org>2009-01-22 19:22:49 +0100
commit41199791234037ce6bf2f9d4afa7248df5b118c7 (patch)
treeb5a8101f88d2d044d9c6065e825022ee513896cd /doc/ext
parent835818b48011446776514fb5cc8f1b80e6779d96 (diff)
downloadsphinx-41199791234037ce6bf2f9d4afa7248df5b118c7.tar.gz
A bit of clarification about where Sphinx finds autodoced modules.
Diffstat (limited to 'doc/ext')
-rw-r--r--doc/ext/autodoc.rst7
1 files changed, 7 insertions, 0 deletions
diff --git a/doc/ext/autodoc.rst b/doc/ext/autodoc.rst
index 993f971a..3e5ce3e1 100644
--- a/doc/ext/autodoc.rst
+++ b/doc/ext/autodoc.rst
@@ -12,6 +12,13 @@
This extension can import the modules you are documenting, and pull in
documentation from docstrings in a semi-automatic way.
+.. note::
+
+ For Sphinx (actually, the Python interpreter that executes Sphinx) to find
+ your module, it must be importable. That means that the module or the
+ package must be in one of the directories on :data:`sys.path` -- adapt your
+ :data:`sys.path` in the configuration file accordingly.
+
For this to work, the docstrings must of course be written in correct
reStructuredText. You can then use all of the usual Sphinx markup in the
docstrings, and it will end up correctly in the documentation. Together with