source: python/trunk/Doc/library/pydoc.rst

Last change on this file was 391, checked in by dmik, 11 years ago

python: Merge vendor 2.7.6 to trunk.

  • Property svn:eol-style set to native
File size: 3.3 KB
RevLine 
[2]1:mod:`pydoc` --- Documentation generator and online help system
2===============================================================
3
4.. module:: pydoc
5 :synopsis: Documentation generator and online help system.
6.. moduleauthor:: Ka-Ping Yee <ping@lfw.org>
7.. sectionauthor:: Ka-Ping Yee <ping@lfw.org>
8
9
10.. versionadded:: 2.1
11
12.. index::
13 single: documentation; generation
14 single: documentation; online
15 single: help; online
16
[391]17**Source code:** :source:`Lib/pydoc.py`
18
19--------------
20
[2]21The :mod:`pydoc` module automatically generates documentation from Python
22modules. The documentation can be presented as pages of text on the console,
23served to a Web browser, or saved to HTML files.
24
25The built-in function :func:`help` invokes the online help system in the
26interactive interpreter, which uses :mod:`pydoc` to generate its documentation
27as text on the console. The same text documentation can also be viewed from
28outside the Python interpreter by running :program:`pydoc` as a script at the
29operating system's command prompt. For example, running ::
30
31 pydoc sys
32
33at a shell prompt will display documentation on the :mod:`sys` module, in a
34style similar to the manual pages shown by the Unix :program:`man` command. The
35argument to :program:`pydoc` can be the name of a function, module, or package,
36or a dotted reference to a class, method, or function within a module or module
37in a package. If the argument to :program:`pydoc` looks like a path (that is,
38it contains the path separator for your operating system, such as a slash in
39Unix), and refers to an existing Python source file, then documentation is
40produced for that file.
41
42.. note::
43
44 In order to find objects and their documentation, :mod:`pydoc` imports the
45 module(s) to be documented. Therefore, any code on module level will be
46 executed on that occasion. Use an ``if __name__ == '__main__':`` guard to
47 only execute code when a file is invoked as a script and not just imported.
48
[391]49Specifying a ``-w`` flag before the argument will cause HTML documentation
[2]50to be written out to a file in the current directory, instead of displaying text
51on the console.
52
[391]53Specifying a ``-k`` flag before the argument will search the synopsis
[2]54lines of all available modules for the keyword given as the argument, again in a
55manner similar to the Unix :program:`man` command. The synopsis line of a
56module is the first line of its documentation string.
57
58You can also use :program:`pydoc` to start an HTTP server on the local machine
[391]59that will serve documentation to visiting Web browsers. :program:`pydoc -p 1234`
60will start a HTTP server on port 1234, allowing you to browse
[2]61the documentation at ``http://localhost:1234/`` in your preferred Web browser.
[391]62:program:`pydoc -g` will start the server and additionally bring up a
[2]63small :mod:`Tkinter`\ -based graphical interface to help you search for
64documentation pages.
65
66When :program:`pydoc` generates documentation, it uses the current environment
[391]67and path to locate modules. Thus, invoking :program:`pydoc spam`
[2]68documents precisely the version of the module you would get if you started the
69Python interpreter and typed ``import spam``.
70
71Module docs for core modules are assumed to reside in
72http://docs.python.org/library/. This can be overridden by setting the
73:envvar:`PYTHONDOCS` environment variable to a different URL or to a local
74directory containing the Library Reference Manual pages.
75
Note: See TracBrowser for help on using the repository browser.