Skip to main content
Change of provenance

The repository or configuration that created this release differ from a previous release. View details.

plain-parser

Python parser for ***plain specification files.

Reads a .plain module and its import / requires chain, resolves Liquid templates, validates concepts and linked resources, and returns the marshalled specification tree plus the ordered list of functionalities (FRIDs).

Install

pip install plain-parser

Command line

plain-parser check <file.plain> [--template-dir DIR] [--config-name NAME]
plain-parser parse <file.plain> [--template-dir DIR] [--config-name NAME]

Both commands parse the module and its requires chain, check that every linked resource is an existing file (not a directory), and walk the module's functionalities. They stop at the first error.

check

Validates the module. In addition to the steps above it reads every linked file and rejects binary files and files holding a large base64 blob.

$ plain-parser check my_spec.plain
my_spec.plain: OK

Exit 0 when the module is valid. On an error, Error: … is written to stderr and the exit code is 1.

parse

Prints the parse result as one UTF-8 JSON document on stdout. Linked files are located but not read.

$ plain-parser parse my_spec.plain
{
  "format_version": 1,
  "modules": [{"module": "...", "tree": {...}}, ...],
  "resources": {...}
}
  • format_version: 1.
  • modules: every module in the requires chain, in build order: deepest ancestor first, the module itself last. Each entry has the module name and its specification tree, in the shape described under Python below.
  • resources: every linked-resource target in the chain, as written in the spec, mapped to the path it resolves to, relative to the entry module's directory, with / as separator: notes.md when found next to the module, ../tpl/notes.md when found in a template directory. The directory part is lexical (symlinks not resolved) and the target is appended as written (.. kept), so joining the value onto the entry module's directory names the file the parser matched. When no relative path exists (another drive on Windows) the value is the absolute path, still with /. Two spellings of one file (notes.md, ./notes.md) are two keys.

Exit 0 on success. On a parser error the JSON is {"format_version": 1, "type": "<error class>", "message": "…"} and the exit code is 1.

Options and exit codes

Modules and {% include %} templates are looked up in the .plain file's directory, then in --template-dir. When --template-dir is not given, it is read from the template-dir key of config.yaml (or the file named by --config-name), found next to the .plain file or in the working directory. Finding it in both is a usage error. The config file is read even when --template-dir is given, so a malformed one fails the run either way. Other config keys are ignored.

Exit code Meaning
0 Success
1 The module, its chain, or a linked resource is invalid
2 Usage error, including an ambiguous or malformed config file
130 Interrupted

Python

from plain_parser import plain_file_parser

module_name, plain_source_tree, required_modules = plain_file_parser("my_spec.plain", ["."])

plain_source_tree is a dict keyed by section (definitions, implementation reqs, test reqs, functional specs), each a list of {"markdown": ..., "linked_resources": [...]} entries. plain_parser.plain_spec has helpers for walking functionalities (get_frids, get_specifications_for_frid, collect_linked_resources).

Development

uv venv --python 3.11 && source .venv/bin/activate
uv pip install -e ".[dev]"
pytest
black . --check && isort . --check-only && flake8 . && mypy src

License

MIT, see LICENSE.

Metadata

Release files for plain-parser 0.1.4

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Change of provenance

The repository or configuration that created these release files differ from that of a previous release.

We recommend inspecting the repository and configuration before proceeding. View details.

Source distribution (sdist)

Source distribution for plain-parser 0.1.4
File Size Uploaded Provenance Actions
plain_parser-0.1.4.tar.gz 88.7 kB With provenance Details for plain_parser-0.1.4.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for plain-parser 0.1.4
File Interpreter ABI Platform Actions
plain_parser-0.1.4-py3-none-any.whl Python 3 none any Details for plain_parser-0.1.4-py3-none-any.whl

Total release size: 118.9 kB

Release files / plain_parser-0.1.4.tar.gz

Change of provenance

This file belongs to a release with changed provenance: the repository or configuration that created the release files differ from that of a previous release.

We recommend inspecting the repository and configuration before proceeding. View details.

Download URL plain_parser-0.1.4.tar.gz
Size 88.7 kB
Tags Source
SHA-256 checksum
How to use checksums
8ef5f81ccf7f3864ff6c9068912a581a2cd1a1a68365935dec86264c99e261e9
BLAKE2b-256 checksum
How to use checksums
fe2207a2d9a9421d973ff9cdd88d3324fd3572690c0c6ee5d2d0a784755eee49
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 28, 2026.

Transparency log

Release files / plain_parser-0.1.4-py3-none-any.whl

Change of provenance

This file belongs to a release with changed provenance: the repository or configuration that created the release files differ from that of a previous release.

We recommend inspecting the repository and configuration before proceeding. View details.

Download URL plain_parser-0.1.4-py3-none-any.whl
Size 30.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
e92bc5c7b1df7aecb3a967caf870b1ff138bd47f102ad34c820d2a1c731f53ee
BLAKE2b-256 checksum
How to use checksums
fd4c4ec09d2ecbb14684aa29a8fc6353910087891741c0b8c5d7c0b25102d962
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 28, 2026.

Transparency log

Security for plain-parser 0.1.4

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.

Change of provenance

The configuration that created this release differs from a previous release.

While this could reflect a routine change by the project maintainers, it may also indicate that the release files have been compromised.

Select from 2 files

Attestation for plain_parser-0.1.4.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 28, 2026.

Transparency log

A 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.

Release history Release notifications | RSS feed

This release

0.1.4 This release

2 release files Change of provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page