scverse-doc
The shared Sphinx theme and documentation configuration for scverse packages.
Install it, and a package's conf.py becomes:
extensions = ["scverse_doc"]
source_repository = "https://github.com/scverse/pertpy"
That gets you the scverse brand and dark mode, the shared sidebar layout, footer, and announcement banner, a "scverse packages" dropdown generated from the package registry, cross-links to every core package, the repository links ("edit this page" and the header icon), and the standard extension stack.
Every piece also works on its own. For the theme without the extension stack or the shared defaults, select it and leave extensions alone – it is a registered Sphinx theme, so installing the package is enough:
html_theme = "scverse"
source_repository = "https://github.com/scverse/pertpy"
Getting started
Please refer to the documentation, in particular, the API documentation. The kitchen sink shows every construct the theme styles, in both colour schemes.
Installation
You need to have Python 3.12 or newer installed on your system. If you don't have Python installed, we recommend installing uv.
We recommend managing dependencies in project-specific virtual environments to avoid dependency conflicts. This is most convenient using package managers such as uv. Choose from the options below to install scverse-doc:
-
Add the latest release of
scverse-docfrom PyPI to youruvproject:uv add 'scverse-doc[full]'
-
Install the latest release into a standard virtual environment:
(after activating your venv) pip install 'scverse-doc[full]'
-
Install the latest development version:
pip install 'scverse-doc[full] @ git+https://github.com/scverse/scverse-doc.git' # (or `uv add`)
The full extra is what extensions = ["scverse_doc"] needs.
For less, pick from the theme extra (for html_theme = "scverse") and the config extra (for scverse_doc.config’s extension stack).
scverse_doc.autodoc, scverse_doc.napoleon, scverse_doc.registry and scverse_doc.source need no extra.
Release notes
See the changelog.
Contact
For questions and help requests, you can reach out in the scverse discourse. If you found a bug, please use the issue tracker.
Citation
t.b.a
1 maintainer
Metadata
1 maintainer
Release files for scverse-doc 0.3.0
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 | |
|---|---|---|---|---|
| scverse_doc-0.3.0.tar.gz | 48.5 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| scverse_doc-0.3.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 92.9 kB
Release files / scverse_doc-0.3.0.tar.gz
| Download URL | scverse_doc-0.3.0.tar.gz |
|---|---|
| Size | 48.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6fe7583dcf6d96e6dc40e5fab024096f770e643b6fc960a7c9b1ee68651e7ab9
|
|
BLAKE2b-256 checksum How to use checksums |
b941f3f09ae21a26f6b7ad7a6e180a9e9b802304ec4700c12a8e5df6ada4b04f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Oct 22, 2026.
Transparency logRelease files / scverse_doc-0.3.0-py3-none-any.whl
| Download URL | scverse_doc-0.3.0-py3-none-any.whl |
|---|---|
| Size | 44.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
705f6ba36a00abf11e2d3fa63db781b1b18a266af50f0dd3a6d949a27e9799ea
|
|
BLAKE2b-256 checksum How to use checksums |
08a2b618eb5dc86792ab53f6f381068793d524d8ba046adafc2b71e6d450be91
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Oct 22, 2026.
Transparency logSecurity for scverse-doc 0.3.0
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 scverse_doc-0.3.0.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 Oct 22, 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.
