cpython/Doc
Éric Araujo 45fc8713bd Make distutils error messages more helpful (#11599).
When running external programs such as a C compiler and getting an
error code, distutils only prints the program name.  With this change,
one can get the full command line by setting the DISTUTILS_DEBUG
environment variable.

This should have no compatibility issues, unless there are tools
that depend on the exact format of distutils debug messages.
2014-03-13 04:55:35 -04:00
..
c-api Fix note markup (#16805). 2014-03-12 19:51:00 -04:00
data Issue #18085: Add missed const modifier for some entries in refcounts.dat. 2013-07-11 21:57:34 +03:00
distutils Make distutils error messages more helpful (#11599). 2014-03-13 04:55:35 -04:00
extending Issue #19407: add Python Packaging User Guide notes 2013-12-10 21:24:55 +10:00
faq Fix note markup (#16805). 2014-03-12 19:51:00 -04:00
howto fix typo (closes #20892) 2014-03-11 13:59:37 -05:00
includes Issue #14428: Use the new time.perf_counter() and time.process_time() functions 2012-04-29 03:01:20 +02:00
install Make distutils error messages more helpful (#11599). 2014-03-13 04:55:35 -04:00
library remove unnecessary word (closes #19060) 2014-03-12 21:41:35 -05:00
reference #19953: Clarify the wording of the augmented assignment discussion. 2014-03-09 18:51:16 -04:00
tools Closes #20090: update Doc/README and the error message in sphinx-build.py to make 2014-03-10 19:26:57 +01:00
tutorial #20740: desquarify 2. 2014-02-24 20:58:31 +02:00
using Issue #20265: Updated some parts of the Using Windows document. 2014-01-17 15:23:42 -06:00
whatsnew Fix grammar. 2014-01-25 05:11:43 -05:00
Makefile Closes #20258: Sphinx toolchain: move back to Jinja2 2.3.1 with support for Py2.5. 2014-01-14 12:00:45 +01:00
README.txt Closes #20090: update Doc/README and the error message in sphinx-build.py to make 2014-03-10 19:26:57 +01: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 Introduce support for documenting which C API elements are not part of the stable/limited API. 2013-10-12 19:54:30 +02:00
contents.rst Remove packaging from the standard library. 2012-06-24 00:07:41 -04:00
copyright.rst update copyright year 2013-12-31 22:02:22 -06:00
glossary.rst #16728: Mention collections.abc.Sequence in 'sequence' glossary entry 2014-02-15 17:05:26 -05:00
license.rst update copyright year 2013-12-31 22:02:22 -06:00
make.bat Closes #20258: Sphinx toolchain: move back to Jinja2 2.3.1 with support for Py2.5. 2014-01-14 12:00:45 +01:00

README.txt

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 http://docs.python.org/download/.

Documentation on the authoring Python documentation, including information about
both style and markup, is available in the "Documenting Python" chapter of the
documentation.


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

You need to have Python 2 installed; the toolset used to build the
docs is written in Python.  It is called *Sphinx*, it is not included in this
tree, but maintained separately.  Also needed are the docutils, supplying the
base markup that Sphinx uses, Jinja, a templating engine, and optionally
Pygments, a code highlighter.


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

Luckily, a Makefile has been prepared so that on Unix, provided you have
installed Python and Subversion, you can just run ::

   make html

to check out the necessary toolset in the `tools/` subdirectory and build the
HTML output files.  To view the generated HTML, point your favorite browser at
the top-level index `build/html/index.html` after running "make".

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=/usr/bin/python2.5

Available make targets are:

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

 * "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.

 * "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.

A "make update" updates the Subversion checkouts in `tools/`.


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

Install the Sphinx package and its dependencies from PyPI.

Then, from the ``Docs`` 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.
----------------------------------------------------------------------