TeachBooks Sphinx extension: Rich hover over tips
Rich tool tips in your TeachBook!
Introduction
Sphinx-tippy allows you to create rich hover over tips as demonstrated here: https://sphinx-tippy.readthedocs.io/en/latest/. This TeachBooks Tippy extension makes it plug-and-play within a TeachBook.
The differences with Sphinx-tippy are:
- Default inclusion of useful CSS-file.
- Default activation of sphinx.ext.mathjax.
- Default loading method of defer changed to None for supporting JavaScript.
- Default support for TeachBooks Sphinx Grasple such that images are shown (as iframes are not loaded).
- Limit the showing of tool tips to the
<main>anchor of the Sphinx book. - Limit the maximum height of a tool tip.
- Force tool tips to remain with visible document body.
- No arrow that points from the tool tip to the link.
What does it do?
You can see how the this works in the example book.
Installation
To install TeachBooks-Sphinx-Tippy, follow these steps:
Step 1: Install the Package
Install the teachbooks-sphinx-tippy package using pip:
pip install teachbooks-sphinx-tippy
Step 2: Add to requirements.txt
Make sure that the package is included in your project's requirements.txt to track the dependency:
teachbooks-sphinx-tippy
Step 3: Enable in _config.yml
In your _config.yml file, add the extension to the list of Sphinx extra extensions (important: underscore, not dash this time):
sphinx:
extra_extensions:
- teachbooks_sphinx_tippy
Usage
By following the steps above, the extension will be added automatically.
Contribute
This tool's repository is stored on GitHub. The README.md of the branch Manual is also part of the TeachBooks manual as a submodule. If you'd like to contribute, you can create a fork and open a pull request on the GitHub repository. To update the README.md shown in the TeachBooks manual, create a fork and open a merge request for the GitHub repository of the manual. If you intent to clone the manual including its submodules, clone using: git clone --recurse-submodulesgit@github.com:TeachBooks/manual.git.
Metadata
Release files for teachbooks-sphinx-tippy 1.0.15
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| teachbooks_sphinx_tippy-1.0.15.tar.gz | 124.1 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| teachbooks_sphinx_tippy-1.0.15-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 137.6 kB
Release files / teachbooks_sphinx_tippy-1.0.15.tar.gz
| Download URL | teachbooks_sphinx_tippy-1.0.15.tar.gz |
|---|---|
| Size | 124.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e5825d2ef38c4ecbada0e169f3f934ba71a86568c2d46e5cb84bcc06b144cc72
|
|
BLAKE2b-256 checksum How to use checksums |
e0829cd6b98feeccf2b0d3153c52b9c8dc235fd70fb0d0cc6984ddd0429f97a7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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, 2025.
Transparency logRelease files / teachbooks_sphinx_tippy-1.0.15-py3-none-any.whl
| Download URL | teachbooks_sphinx_tippy-1.0.15-py3-none-any.whl |
|---|---|
| Size | 13.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
eca60b7f99005861d161db76b2ab65349e61022c219f5fe781779fc91c1d7a99
|
|
BLAKE2b-256 checksum How to use checksums |
05778c5a7237bc99221408f12b629210b8f2176bcccfca916c09edfa8eb048e3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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, 2025.
Transparency log