Examples with executable code and visuals
Introduction
This Sphinx extension provides an interface to examples with executable code and visuals.
This extension includes code adapted from sphinx-exercise.
Installation
To install the Sphinx-Code-Examples extension, follow these steps:
Step 1: Install the Package
Install the Sphinx-Code-Examples package using pip:
pip install sphinx-code-examples
Step 2: Add to requirements.txt
Make sure that the package is included in your project's requirements.txt to track the dependency:
sphinx-code-examples
Step 3: Enable in _config.yml
In your _config.yml file, add the extension to the list of Sphinx extra extensions:
sphinx:
extra_extensions:
- sphinx_code_examples
Documentation
Further documentation for this extension is available in the TeachBooks manual.
1 maintainer
Metadata
1 maintainer
Release files for sphinx-code-examples 1.2.3
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_code_examples-1.2.3.tar.gz | 31.0 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| sphinx_code_examples-1.2.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 103.1 kB
Release files / sphinx_code_examples-1.2.3.tar.gz
| Download URL | sphinx_code_examples-1.2.3.tar.gz |
|---|---|
| Size | 31.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4845be7934326cd2ace945c740acce3420c8aebaebb6eb1655c73cfecc159eb7
|
|
BLAKE2b-256 checksum How to use checksums |
cb64fe4dbc167754e2e8eface54101d732a55498f27cc85bfe824c24493979e5
|
| 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 Jan 4, 2026.
Transparency logRelease files / sphinx_code_examples-1.2.3-py3-none-any.whl
| Download URL | sphinx_code_examples-1.2.3-py3-none-any.whl |
|---|---|
| Size | 72.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f2f25cd5fecc0e666fcbbd41016a6545bee0a7ae4d19c8c68ad70fac1171c596
|
|
BLAKE2b-256 checksum How to use checksums |
b09ee9d545c5c699cd6fa35912b487cde2910e4c5fcf7e4f52fced2f31dd8cdc
|
| 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 Jan 4, 2026.
Transparency logSecurity for sphinx-code-examples 1.2.3
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_code_examples-1.2.3.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 Jan 4, 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.
