Sphinx Fortran Domain
Fortran-lang's base Sphinx domain to document Fortran projects.
Status: This project is preparing its first official 0.1.x release. The core API is usable and tested; feedback and issue reports are welcome.
- Changelog: CHANGELOG.md
Install
For regular usage:
pip install sphinx-fortran-domain
For editable install for development:
pip install -e .
Build the docs
Install with documentation dependencies:
pip install -e ".[docs]"
Build HTML documentation:
cd docs
make html
Enable the extension
In conf.py:
extensions = [
"sphinx_fortran_domain",
]
# Where your Fortran sources live (directories, files, or glob patterns)
fortran_sources = [
"../src", # directory
"../example/*.f90", # glob pattern
]
# Exclude sources from parsing (directories, files, or glob patterns)
fortran_sources_exclude = [
"../example/legacy", # directory
"../example/skip_this.f90", # file
"../example/**/generated_*.f90", # glob
]
# Select a lexer (built-in: "regex")
fortran_lexer = "regex"
# Doc comment convention
# Examples: '!>' or '!!' or '!@'
fortran_doc_chars = [">", "!"]
Directives and roles
Manual declarations (create targets for cross-references):
.. f:function:: add_vectors(vec1, vec2)
.. f:subroutine:: normalize_vector(vec)
Autodoc-style views from parsed sources:
.. f:module:: example_module
.. f:submodule:: stdlib_quadrature_trapz
.. f:program:: test_program
Cross-references:
See :f:mod:`example_module` and :f:subr:`normalize_vector`.
Writing a lexer plugin
See the full step-by-step guide in the documentation: docs/api/lexers.rst.
External packages can register a lexer at import/setup time:
from sphinx_fortran_domain.lexers import register_lexer
def setup(app):
register_lexer("my-lexer", lambda: MyLexer())
Then use fortran_lexer = "my-lexer".
Math in doc comments
This extension parses Fortran doc comments as reStructuredText fragments, so Sphinx
roles/directives work inside docs (including math when sphinx.ext.mathjax is enabled).
Supported math styles:
- Recommended (reST):
!> .. math:: \hat{v} = \frac{\vec{v}}{|\vec{v}|}
Inline math also works via :math::
!> The magnitude is :math:`|\vec{v}| = \sqrt{x^2 + y^2 + z^2}`.
Community
- Contributing guide: CONTRIBUTING.md
- Code of conduct: CODE_OF_CONDUCT.md
Metadata
Release files for sphinx-fortran-domain 0.2.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 | |
|---|---|---|---|---|
| sphinx_fortran_domain-0.2.0.tar.gz | 44.7 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| sphinx_fortran_domain-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 83.5 kB
Release files / sphinx_fortran_domain-0.2.0.tar.gz
| Download URL | sphinx_fortran_domain-0.2.0.tar.gz |
|---|---|
| Size | 44.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
25e5a77121fe7460bb53a14eb99051ce4021c7af589e23d3e2a3d0fc6b1c1321
|
|
BLAKE2b-256 checksum How to use checksums |
b520ab5139342c7182f974d13e5e13755c3f8c57069e97e127095eafa6c92b3c
|
| 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 19, 2026.
Transparency logRelease files / sphinx_fortran_domain-0.2.0-py3-none-any.whl
| Download URL | sphinx_fortran_domain-0.2.0-py3-none-any.whl |
|---|---|
| Size | 38.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f30e17d4b4abb7f411a1c8d899f0c1f2674e4c7cf9782917ec5ad1392fa1d9bf
|
|
BLAKE2b-256 checksum How to use checksums |
cfa58e7332c7cb64bca1cefecc7067a640e0ea36dd28d6a0de7722de92d24d01
|
| 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 19, 2026.
Transparency logSecurity for sphinx-fortran-domain 0.2.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 sphinx_fortran_domain-0.2.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 19, 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.