Skip to main content

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:

  1. Add the latest release of scverse-doc from PyPI to your uv project:

    uv add 'scverse-doc[full]'
    
  2. Install the latest release into a standard virtual environment:

    (after activating your venv)
    pip install 'scverse-doc[full]'
    
  3. 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

Metadata

Release files for scverse-doc 0.1.0.post0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for scverse-doc 0.1.0.post0
File Size Uploaded
scverse_doc-0.1.0.post0.tar.gz 40.9 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for scverse-doc 0.1.0.post0
File Interpreter ABI Platform
scverse_doc-0.1.0.post0-py3-none-any.whl Python 3 none any Details

Total release size: 78.4 kB

Release files / scverse_doc-0.1.0.post0.tar.gz

Download URL scverse_doc-0.1.0.post0.tar.gz
Size 40.9 kB
Tags Source
SHA-256 checksum
How to use checksums
b2dddfeb32e282da230f6c917b167d5b202ab17c7ed1f32d125a6e5d646cc881
BLAKE2b-256 checksum
How to use checksums
304de99aefc62e3489bf8addb98185cfbc36b07c487dacd2fa64a3574fda6297
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 13, 2026.

Transparency log

Release files / scverse_doc-0.1.0.post0-py3-none-any.whl

Download URL scverse_doc-0.1.0.post0-py3-none-any.whl
Size 37.5 kB
Tags Python 3
SHA-256 checksum
How to use checksums
84b24c405a3a9f65241f33e491bb0fa26ae95a81ee1c653076b74b1531d66429
BLAKE2b-256 checksum
How to use checksums
0e37bb172600563f081f034fd6ff4eb2b411aebb2a7ff198ace48a4504d117bc
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 13, 2026.

Transparency log

Release history Release notifications | RSS feed

0.1.1

2 release files

This release

0.1.0.post0 This release

2 release files

0.0.1

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page