cpython/Doc
2014-09-14 23:37:03 -07:00
..
c-api Issue #18395, #22108: Update embedded Python examples to decode correctly 2014-08-01 12:28:49 +02:00
data Issue #20517: Removed unnecessary new (short-lived) functions from PyErr. 2014-02-10 03:43:57 -08:00
distributing Issue #22295: Adopt 'python -m pip' as the preferred invocation 2014-09-06 20:38:23 +10:00
distutils Merge with 3.4 2014-06-13 14:58:09 -04:00
extending Issue #18395, #22108: Update embedded Python examples to decode correctly 2014-08-01 12:28:49 +02:00
faq y2k compliance, lol (closes #22380) 2014-09-10 17:13:06 -04:00
howto Issue #13689: Merge from 3.4. 2014-07-01 06:03:24 +03:00
includes Issue #18395, #22108: Update embedded Python examples to decode correctly 2014-08-01 12:28:49 +02:00
install Merge in all documentation changes since branching 3.4.0rc1. 2014-03-15 21:13:56 -07:00
installing Issue #22295: Adopt 'python -m pip' as the preferred invocation 2014-09-06 20:38:23 +10:00
library Fix full-stop whitespace in configparser docs 2014-09-14 23:37:03 -07:00
reference Issue #20643: Removed unneeded (and wrong) class directives. 2014-09-05 23:28:19 +03:00
tools merge 3.4 2014-09-13 01:45:50 -04:00
tutorial #22170: merge with 3.4. 2014-08-08 17:24:06 +03:00
using asyncio: document the debug mode 2014-06-23 00:36:11 +02:00
whatsnew Issue #16104: Allow compileall to do parallel bytecode compilation. 2014-09-12 10:39:48 -04:00
about.rst Issue #20255: Update the about and bugs pages. 2014-01-14 16:03:11 -06:00
bugs.rst Issue #20255: Update the about and bugs pages. 2014-01-14 16:03:11 -06:00
conf.py Merge in all documentation changes since branching 3.4.0rc1. 2014-03-15 21:13:56 -07:00
contents.rst Merge in all documentation changes since branching 3.4.0rc1. 2014-03-15 21:13:56 -07:00
copyright.rst update copyright year 2013-12-31 22:02:22 -06:00
glossary.rst Merge issue #22295 fix from 3.4 2014-09-06 20:40:00 +10:00
license.rst Final documentation fixes for 3.4.0 final. 2014-03-15 22:43:17 -07:00
make.bat Issue #21688: Give informative error message when hhc.exe cannot be found. 2014-06-10 12:07:45 -05:00
Makefile Issue #15759: "make suspicious", "make linkcheck" and "make doctest" in Doc/ 2014-07-22 10:24:25 +03:00
README.txt Closes #17386: Merge with 3.4 2014-04-29 09:47:39 -05:00

Python Documentation README
~~~~~~~~~~~~~~~~~~~~~~~~~~~

This directory contains the reStructuredText (reST) sources to the Python
documentation.  You don't need to build them yourself, prebuilt versions are
available at <https://docs.python.org/dev/download.html>.

Documentation on authoring Python documentation, including information about
both style and markup, is available in the "Documenting Python" chapter of the
developers guide <http://docs.python.org/devguide/documenting.html>.


Building the docs
=================

You need to have Sphinx <http://sphinx-doc.org/> installed; it is the toolset
used to build the docs.  It is not included in this tree, but maintained
separately and available from PyPI <http://pypi.python.org/pypi/Sphinx>.


Using make
----------

A Makefile has been prepared so that on Unix, provided you have installed
Sphinx, you can just run ::

   make html

to build the HTML output files.

On Windows, we try to emulate the Makefile as closely as possible with a
``make.bat`` file.

To use a Python interpreter that's not called ``python``, use the standard
way to set Makefile variables, using e.g. ::

   make html PYTHON=python3

On Windows, set the PYTHON environment variable instead.

To use a specific sphinx-build (something other than ``sphinx-build``), set
the SPHINXBUILD variable.

Available make targets are:

 * "clean", which removes all build files.

 * "html", which builds standalone HTML files for offline viewing.

 * "htmlview", which re-uses the "html" builder, but then opens the main page
   in your default web browser.

 * "htmlhelp", which builds HTML files and a HTML Help project file usable to
   convert them into a single Compiled HTML (.chm) file -- these are popular
   under Microsoft Windows, but very handy on every platform.

   To create the CHM file, you need to run the Microsoft HTML Help Workshop
   over the generated project (.hhp) file.  The make.bat script does this for
   you on Windows.

 * "latex", which builds LaTeX source files as input to "pdflatex" to produce
   PDF documents.

 * "text", which builds a plain text file for each source file.

 * "epub", which builds an EPUB document, suitable to be viewed on e-book
   readers.

 * "linkcheck", which checks all external references to see whether they are
   broken, redirected or malformed, and outputs this information to stdout as
   well as a plain-text (.txt) file.

 * "changes", which builds an overview over all versionadded/versionchanged/
   deprecated items in the current version. This is meant as a help for the
   writer of the "What's New" document.

 * "coverage", which builds a coverage overview for standard library modules and
   C API.

 * "pydoc-topics", which builds a Python module containing a dictionary with
   plain text documentation for the labels defined in
   `tools/sphinxext/pyspecific.py` -- pydoc needs these to show topic and
   keyword help.

 * "suspicious", which checks the parsed markup for text that looks like
   malformed and thus unconverted reST.

 * "check", which checks for frequent markup errors.

 * "serve", which serves the build/html directory on port 8000.

 * "dist", (Unix only) which creates distributable archives of HTML, text,
   PDF, and EPUB builds.


Without make
------------

Install the Sphinx package and its dependencies from PyPI.

Then, from the ``Doc`` directory, run ::

   sphinx-build -b<builder> . build/<builder>

where ``<builder>`` is one of html, text, latex, or htmlhelp (for explanations
see the make targets above).


Contributing
============

Bugs in the content should be reported to the Python bug tracker at
http://bugs.python.org.

Bugs in the toolset should be reported in the Sphinx bug tracker at
http://www.bitbucket.org/birkenfeld/sphinx/issues/.

You can also send a mail to the Python Documentation Team at docs@python.org,
and we will process your request as soon as possible.

If you want to help the Documentation Team, you are always welcome.  Just send
a mail to docs@python.org.


Copyright notice
================

The Python source is copyrighted, but you can freely use and copy it
as long as you don't change or remove the copyright notice:

----------------------------------------------------------------------
Copyright (c) 2000-2014 Python Software Foundation.
All rights reserved.

Copyright (c) 2000 BeOpen.com.
All rights reserved.

Copyright (c) 1995-2000 Corporation for National Research Initiatives.
All rights reserved.

Copyright (c) 1991-1995 Stichting Mathematisch Centrum.
All rights reserved.

See the file "license.rst" for information on usage and redistribution
of this file, and for a DISCLAIMER OF ALL WARRANTIES.
----------------------------------------------------------------------