Sphinx is a tool that makes it easy to create intelligent and beautiful documentation for Python projects (or other documents consisting of multiple reStructuredText sources), written by Georg Brandl. It was originally created for the new Python documentation, and has excellent facilities for Python project documentation, but C/C++ is supported as well, and more languages are planned.
Sphinx uses reStructuredText as its markup language, and many of its strengths come from the power and straightforwardness of reStructuredText and its parsing and translating suite, the Docutils.
Among its features are the following:
Output formats: HTML (including derivative formats such as HTML Help, Epub and Qt Help), plain text, manual pages and LaTeX or direct PDF output using rst2pdf
Extensive cross-references: semantic markup and automatic links for functions, classes, glossary terms and similar pieces of information
Hierarchical structure: easy definition of a document tree, with automatic links to siblings, parents and children
Automatic indices: general index as well as a module index
Code handling: automatic highlighting using the Pygments highlighter
Flexible HTML output using the Jinja 2 templating engine
Various extensions are available, e.g. for automatic testing of snippets and inclusion of appropriately formatted docstrings
Setuptools integration
For more information, refer to the the documentation.
Installation
Sphinx is published on PyPI and can be installed from there:
pip install -U sphinx
We also publish beta releases:
pip install -U --pre sphinx
If you wish to install Sphinx for development purposes, refer to the contributors guide.
Documentation
Documentation is available from sphinx-doc.org.
Testing
Continuous testing is provided by Travis (for unit tests and style checks on Linux), AppVeyor (for unit tests on Windows), and CircleCI (for large processes like TeX compilation).
For information on running tests locally, refer to the contributors guide.
Contributing
Refer to the contributors guide.
Release signatures
Releases are signed with following keys:
Release files for Sphinx 1.7.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| Sphinx-1.7.2.tar.gz | 4.7 MB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| Sphinx-1.7.2-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details |
Total release size: 6.7 MB
Release files / Sphinx-1.7.2.tar.gz
| Download URL | Sphinx-1.7.2.tar.gz |
|---|---|
| Size | 4.7 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5a1c9a0fec678c24b9a2f5afba240c04668edb7f45c67ce2ed008996b3f21ae2
|
|
BLAKE2b-256 checksum How to use checksums |
0d12843cdf08c9795d1d225c92e099a18143856110cbeff562b8abd60bd26cec
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / Sphinx-1.7.2-py2.py3-none-any.whl
| Download URL | Sphinx-1.7.2-py2.py3-none-any.whl |
|---|---|
| Size | 1.9 MB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
7a606d77618a753adb79e13605166e3cf6a0e5678526e044236fc1ac43650910
|
|
BLAKE2b-256 checksum How to use checksums |
0c399b723cd9d5a093174e518a7a4cb8ef8b0e067d8a9fcc00fcb445738cc300
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for Sphinx 1.7.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
