wadler-lindig-parts¤
One engine behind repr, str, __format__ and the representations Jupyter
asks for. A type says what it is made of — a tree of roled fragments — and
every output route lays that same tree out its own way.
Add a markup and every registered type gets it. Register a type and it gets every markup, including ones added later by somebody else.
>>> from wadler_lindig_parts.examples import Version
>>> v = Version(2, 1)
>>> v
2.1
>>> f"{v:html}"
'<span>2</span>.<span>1</span>'
>>> f"{v:latex}"
'$2.1$'
All three came out of one pparts method. They cannot drift apart, because
there is only one description of what a Version is.
pip install wadler-lindig-parts
Exactly two runtime dependencies — wadler-lindig and plum-dispatch —
on Python 3.10 through 3.15.
Where to go¤
-
New here, or still deciding. What the package does, whether it fits your type, and a quickstart that prints five ways in fifteen lines.
-
Start here if the package is new to you. Two lessons: build a type that renders itself, then add a word to the format-spec vocabulary.
-
Short answers for people already building something: register a type, nest values, add an axis, add a markup, render your own payload type.
-
The spec grammar, the six axes, what registration refuses, and every public name.
-
Why one renderer rather than four, and what that choice costs.
What a spec looks like¤
A format spec is a --joined run of keywords, optionally ending in an
ordinary Python format spec:
>>> from wadler_lindig_parts.examples import Term
>>> t = Term(2.0, "x")
>>> f"{t:mul}"
'2.0 * x'
>>> f"{t:html-mul}"
'<span>2.0</span> * <span>x</span>'
>>> f"{t:mul-.3f}"
'2.000 * x'
The full rules are in Format spec grammar.