sphinx-section-include
Include selected reStructuredText sections in Sphinx documentation.
$ pip install sphinx-section-includeAdd to conf.py:
"""Sphinx configuration."""
extensions = ["sphinx_section_include"]Include a section:
.. include-section:: manual.rst
:section: Getting started / Configuration
:include-heading:
:exclude-sections: Advanced configurationSelect by exact heading, heading path, or #label. Omit :include-heading: to include only the section’s contents. :exclude-sections: accepts one descendant selector per line. Paths are relative to the including document, or to the Sphinx source directory when prefixed with /.
Extension authors can reuse parsed sources through the Python API.
See the examples and contributor guide.
1 maintainer
Metadata
1 maintainer
Release files for sphinx-section-include 2026.11.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 | Actions |
|---|---|---|---|---|
| sphinx_section_include-2026.11.2.tar.gz | 155.9 kB | With provenance | Details for sphinx_section_include-2026.11.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| sphinx_section_include-2026.11.2-py3-none-any.whl | Python 3 | none | any | Details for sphinx_section_include-2026.11.2-py3-none-any.whl |
Total release size: 165.4 kB
Release files / sphinx_section_include-2026.11.2.tar.gz
| Download URL | sphinx_section_include-2026.11.2.tar.gz |
|---|---|
| Size | 155.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d70fbff520464825621bda0423bbd1ef07b3f8fd0f5dcbd39fecaf6f0335c366
|
|
BLAKE2b-256 checksum How to use checksums |
1539f70192d28f64827cfebcda4619ad4a45610f7912cd24ca186e365595659c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 2, 2026.
Transparency logRelease files / sphinx_section_include-2026.11.2-py3-none-any.whl
| Download URL | sphinx_section_include-2026.11.2-py3-none-any.whl |
|---|---|
| Size | 9.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ee323677025bf713e849ba9abd2d4d66f11a7ad12e79c4e29dc248a8ee0c4eb7
|
|
BLAKE2b-256 checksum How to use checksums |
b05a510ad02c9f42c150e31ed68cc7fdcc0555953c850f28d6cb46f442a2c20b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 2, 2026.
Transparency logSecurity for sphinx-section-include 2026.11.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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for sphinx_section_include-2026.11.2.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 2, 2026.
Transparency logA 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.
