Skip to content


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Main repository for the Sphinx documentation builder
Failed to load latest commit information.
doc fix http/https
sphinx Closes #1748: SyntaxError in sphinx/ext/ with Python 2.6.
tests Closes #1748: SyntaxError in sphinx/ext/ with Python 2.6.
utils Merge branch 'stable'
.gitignore add a .gitignore file, remove .hgignore
.travis.yml Try to work around travis connection issues, see travis-ci/travis-ci#…
AUTHORS Add name to AUTHORS file
CHANGES Closes #1748: SyntaxError in sphinx/ext/ with Python 2.6.
CHANGES.old changelog: split off older changes (pre-1.0) to a CHANGES.old file
EXAMPLES Closes #1735: Use instead of ``http`` protoco…
LICENSE Merge branch 'stable' remove custom_fixers from that directory already removed…
Makefile fix trailing space and long line
README.rst Correct few "typos".
babel.cfg Added improvements about i18n for themes "basic", "haiku" and "scroll… update bundled for setuptools-7.0 that requires Python 2.…
setup.cfg Use universal wheel package. removing build directory procedure is no… fix http/https all: update copyright all: update copyright all: update copyright all: update copyright
test-reqs.txt fix missing test requires
tox.ini Complete test suite overhaul.


README for Sphinx

This is the Sphinx documentation generator, see



python build
sudo python install

Reading the docs

After installing:

cd doc
make html

Then, direct your browser to _build/html/index.html.

Or read them online at <>.


To run the tests with the interpreter available as python, use:

make test

If you want to use a different interpreter, e.g. python3, use:

PYTHON=python3 make test

Continuous testing runs on travis:


  1. Check for open issues or open a fresh issue to start a discussion around a feature idea or a bug.
  2. If you feel uncomfortable or uncertain about an issue or your changes, feel free to email
  3. Fork the repository on GitHub to start making your changes to the master branch for next major version, or stable branch for next minor version.
  4. Write a test which shows that the bug was fixed or that the feature works as expected.
  5. Send a pull request and bug the maintainer until it gets merged and published. Make sure to add yourself to AUTHORS <> and the change to CHANGES <>.
Something went wrong with that request. Please try again.