markdown-include-variants
🚨 Warning: Internal Project
This is an internal project, it is mainly useful for the docs in @tiangolo's projects (e.g. all the FastAPI projects).
It is probably not useful to you. You should probably not use it. 😅
There are no guarantees about behavior, it is made to suit the needs of these projects, to simplify writing documentation.
How to Use
If you're still here it's probably because you are getting involved in one of the projects that use it. 🤓
Here's how it works. 🚀
Configure Plugin in MkDocs Material
Make sure mkdocs.yml has a section with at least these configs:
markdown_extensions:
# Python Markdown Extensions
pymdownx.highlight:
pymdownx.superfences:
# pymdownx blocks
pymdownx.blocks.admonition:
types:
- tip
pymdownx.blocks.details:
pymdownx.blocks.tab:
alternate_style: True
# Other extensions
mdx_include:
markdown_include_variants:
The last config is the one specific to this extension, markdown-include-variants.
The other configs are for the extensions that actually render the output, this extension (markdown-include-variants) just generates the content to be rendered by those other extensions.
Workflow
- You add a Python source example to the
docs_srcdirectory, with the minimum Python version supported by the project, and using the old format withoutAnnotated, if that applies, it would be named something liketutorial001.py. - Copy the file and update it to use
Annotated(if that applies), and name the file with a "tag" (a prefix) of_an, like:tutorial001_an.py. - Run the internal script to generate the variants of the files for superior versions of Python, like
3.9,3.10, etc. (this internal script is in the project itself). This would generate files liketutorial001_py39.py,tutorial001_py310.py, etc. andtutorial001_an_py39.py,tutorial001_an_py310.py, etc. - In the Markdown file, include the preferred version of the file, using this syntax:
{* ./docs_src/first_steps/tutorial001_an_py310.py *}
That will be automatically expanded with mdx-include to include the other variants below in a collapsed details box.
Include Lines
To include specific line ranges, use the config ln:
{* ./docs_src/first_steps/tutorial001_an_py310.py ln[3:6,8,10:11] *}
That will include only:
- lines 3 to 6
- line 8
- lines 10 to 11
It will add blocks with comments in the middle like:
# Code here omitted 👈️
If you include specific lines, it will also add another collapsed details box with the "Full file preview".
Highlight Lines
You can highlight specific lines using the config hl:
{* ./docs_src/first_steps/tutorial001_an_py310.py hl[3,5:7,10] *}
That will highlight:
- line 3
- lines 5 to 7
- line 10
Have in mind that the file path points to the simplest version of the file, the one without the _an suffix. But the main file shown will be the highest (recommended) version, and the highlights will apply to that file.
So, when deciding which lines to highlight, do that based on the highest version of the file.
Include Lines and Highlight
You can combine both ln and hl:
{* ./docs_src/first_steps/tutorial001_an_py310.py ln[3:6,8,10:11] hl[3,5:6,10] *}
The highlighted lines refer to the source file (for the highest/recommended version), not the final rendered code block.
This makes it easier to decide which lines to highlight just by opening the source file, without having to calculate the actual lines in the rendered block after included, the extra lines for comments when omitting lines, etc.
Include Lines and Highlight - Example
For example, you could have a source file with:
print("line 1")
print("line 2")
print("line 3")
print("line 4")
print("line 5")
print("line 6") # highlight this
print("line 7")
Using a declaration like this:
{* ./docs_src/first_steps/tutorial001_an_py310.py ln[5:7] hl[6] *}
Could render something like:
# Code above omitted 👈️
print("line 5")
print("line 6") # highlight this
print("line 7")
Notice that the comment above adds 2 extra lines, and only the desired lines are included, the result is that the actual highlighted line is the rendered line 4, but the source line 6, it's all calculated automatically. 🤓
Include Only File Preview
If you only want to generate the "File Preview" collapsed details section, without actually including a tab of source files, you can use ln[0]:
{* ./docs_src/first_steps/tutorial001_an_py310.py ln[0] *}
This is useful for example at the beginning of a new page, in a recap of the last used file in the previous page.
License
This project is licensed under the terms of the MIT license.
Metadata
Release files for markdown-include-variants 0.0.8
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| markdown_include_variants-0.0.8.tar.gz | 46.9 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| markdown_include_variants-0.0.8-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 55.0 kB
Release files / markdown_include_variants-0.0.8.tar.gz
| Download URL | markdown_include_variants-0.0.8.tar.gz |
|---|---|
| Size | 46.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
46d812340c64dcd3646b1eaa356bafb31626dd7b4955d15c44ff8c48c6357227
|
|
BLAKE2b-256 checksum How to use checksums |
c547ec9eae4a6d2f336d95681df43720e2b25b045dc3ed44ae6d30a5ce2f5dff
|
| 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 Dec 12, 2025.
Transparency logRelease files / markdown_include_variants-0.0.8-py3-none-any.whl
| Download URL | markdown_include_variants-0.0.8-py3-none-any.whl |
|---|---|
| Size | 8.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
425a300ae25fbcd598506cba67859a9dfa047333e869e0ff2e11a5e354b326dc
|
|
BLAKE2b-256 checksum How to use checksums |
4e0e130958e7ec50d13f2ee7b6c142df5c352520a9251baf1652e41262703857
|
| 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 Dec 12, 2025.
Transparency log