fprime-fpp-format
A formatter for the F Prime Prime (FPP) modeling language.
This package ships the fpp-format executable, a pretty-printer for .fpp
source files.
Usage
# Format files in place
fpp-format path/to/model.fpp
# Check formatting without modifying (exit 1 if not formatted)
fpp-format --check path/to/model.fpp
# Format from stdin to stdout
cat path/to/model.fpp | fpp-format --stdin
# Override the indentation width and maximum line length
fpp-format --indent 2 --line-length 100 path/to/model.fpp
Options
| Option | Description |
|---|---|
--check |
Check formatting without writing; exit 1 if a file is unformatted. |
--stdin |
Read from stdin and write to stdout (default when no files given). |
--recursive-includes |
Also follow include specifiers and format reachable .fppi fragments. |
--indent <N> |
Number of spaces per indentation level. Overrides .fpp-format (default: 4). |
--line-length <N> |
Maximum line width before specs explode their clauses. Overrides .fpp-format (default: 80). |
--entry <RULE> |
Select the parser entrypoint / grammar rule (see below). |
--help |
Print usage. |
Configuration file (.fpp-format)
The indentation width and maximum line length can be set project-wide in a
.fpp-format file. Starting from each formatted file's directory, fpp-format
searches upward through parent directories for the nearest .fpp-format file
(the same discovery model as .clang-format). The same file is honored by
fprime-util format and by the language server's format-on-save, so the editor
and CI always agree.
The file is a minimal key = value list; blank lines and # comments are
ignored:
# .fpp-format
indent = 4
line-length = 80
Supported keys:
| Key | Description | Default |
|---|---|---|
indent |
Spaces per indentation level. | 4 |
line-length |
Maximum line width before clauses break. | 80 |
Precedence, lowest to highest: built-in defaults → .fpp-format file →
--indent / --line-length command-line flags. A malformed .fpp-format file
is a hard error on the command line (to avoid formatting with the wrong profile
and reporting false --check failures); the language server logs it and falls
back to defaults so an editor save never fails.
Entrypoint rule (--entry)
The formatter parses input starting from a specific grammar rule. A whole
.fpp file is a module (the default), but other rules are needed when
formatting include fragments.
Supported rules:
module(default)componenttopologytlm-packettlm-packet-set
Recursive include formatting (--recursive-includes)
By default fpp-format formats only the files you name and does not touch
.fppi fragments referenced via include. Pass --recursive-includes to also
follow every include specifier and format the referenced fragments
(recursively):
# Formats model.fpp and every .fppi it (transitively) includes
fpp-format --recursive-includes path/to/model.fpp
With --recursive-includes, include paths are resolved relative to the
including file (matching the parser), each fragment is formatted exactly once
even if included from several places, and include cycles are detected and
reported as an error. The entrypoint for each fragment is derived from the
context of its include — a fragment included in a component { ... } body is
formatted as component members, one in a topology { ... } body as topology
members, and so on, so you do not need --entry for fragments reached this way.
State-machine includes have no standalone entrypoint and are left untouched.
Note: the language-server integration never follows includes; it only ever formats the current document buffer.
Formatting a bare .fppi file
An .fppi file is not a standalone module — it is a fragment that is spliced in
via an include specifier. When you format a fragment directly (rather than
reaching it from a root .fpp), there is no include context to infer the rule
from, so pass --entry to select the matching entrypoint:
# An .fppi included inside a `module { ... }` body (module-level members)
fpp-format --entry module commands.fppi
# An .fppi included inside a `component { ... }` body
fpp-format --entry component ports.fppi
# An .fppi included inside a `topology { ... }` body
fpp-format --entry topology connections.fppi
If you omit --entry, the module rule is used, which is correct for normal
.fpp files and for .fppi fragments containing module-level members.
Release files for fprime-fpp-format 3.3.18
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| fprime_fpp_format-3.3.18.tar.gz | 129.1 kB | Details |
Built distributions (wheels)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| fprime_fpp_format-3.3.18-py3-none-win_amd64.whl | Python 3 | none | Windows x86-64 | Details |
| fprime_fpp_format-3.3.18-py3-none-manylinux_2_17_x86_64.manylinux2014_x86_64.whl | Python 3 | none | Linux glibc 2.17+ x86-64 | Details |
| fprime_fpp_format-3.3.18-py3-none-macosx_11_0_arm64.whl | Python 3 | none | macOS 11.0+ ARM64 | Details |
Total release size: 1.5 MB
Release files / fprime_fpp_format-3.3.18.tar.gz
| Download URL | fprime_fpp_format-3.3.18.tar.gz |
|---|---|
| Size | 129.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ac2d641931a90bd371741a3835423b6de7d565692cdf9e0461858e51984a3429
|
|
BLAKE2b-256 checksum How to use checksums |
b14503b1708a07ac4b0d5fcd0659cb4f34053e47e54fc09601f9e684fdfb942e
|
| 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 Sep 12, 2026.
Transparency logRelease files / fprime_fpp_format-3.3.18-py3-none-win_amd64.whl
| Download URL | fprime_fpp_format-3.3.18-py3-none-win_amd64.whl |
|---|---|
| Size | 420.9 kB |
| Tags | Python 3 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
c752190c49dc34793a5073b6267d53a4a26cb8e37c060f82eabede271ffb57e4
|
|
BLAKE2b-256 checksum How to use checksums |
441a36abf1ca73fcd28e802626a2a9be7be34116ec49055580faf1cd6e5c6e2b
|
| 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 Sep 12, 2026.
Transparency logRelease files / fprime_fpp_format-3.3.18-py3-none-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | fprime_fpp_format-3.3.18-py3-none-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 517.9 kB |
| Tags | Linux glibc 2.17+ x86-64 Python 3 |
|
SHA-256 checksum How to use checksums |
10146c31e77ca1467f29d836b0656143ba6889034806416248e7c0b2b322f4ec
|
|
BLAKE2b-256 checksum How to use checksums |
506131f477dee3629bf0e678691aa79c241459b881cfdcd1414365d153bc8723
|
| 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 Sep 12, 2026.
Transparency logRelease files / fprime_fpp_format-3.3.18-py3-none-macosx_11_0_arm64.whl
| Download URL | fprime_fpp_format-3.3.18-py3-none-macosx_11_0_arm64.whl |
|---|---|
| Size | 471.1 kB |
| Tags | Python 3 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
121171ba5190d2d59ca5eae57f44dc9aeb8dbbfb5cecdad8307df5bc45f27451
|
|
BLAKE2b-256 checksum How to use checksums |
236295f3bd96b30aa83471f70b2ca197d694f52dea504820b5026c62330d60fa
|
| 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 Sep 12, 2026.
Transparency log
