tomlclass
Lossless TOML editing and typed configuration in one zero-dependency package.
Change one value in a config file without breaking a single comment; declare schemas as Python classes to get commented templates, aggregated validation and diff-based write-back.
The configuration semantics come from the ErisPulse framework's config system.
Versioning: tomlclass is pre-1.0 and does not strictly follow SemVer yet. Before the project stabilizes, minor version bumps may include new API additions — existing APIs will remain backward compatible.
Features
- Lossless editing engine: TOML 1.0/1.1 parse and write-back; the only library with a perfect 187/187 on toml-test 1.5.0 valid tests. Untouched documents render byte-identical to input
- TOML 1.1 with a version dial:
\e/\xescapes, seconds-optional times, newlines and trailing commas in inline tables, non-ASCII bare keys — on by default; passtoml_version="1.0"toparse/loads/load/update/Config.loadfor strict legacy rejection semantics - None your way: opt-in rtoml-style
none_valuesentinel —dumps(data, none_value="@None")andloads(text, none_value="@None")round-tripNonethrough TOML strings - One-line updates:
tomlclass.update("app.toml", {"server.port": 9090})— read, change, atomically write back; comments, ordering and formatting survive everywhere else - Typed config: declare the schema as classes — docstrings become template comments, validation aggregates all errors with each field's documented intent, defaults are merged in memory and never written back
- Comment operations: read, replace and delete comments per key; schema descriptions can be injected as comments (three strategies)
- tomllib compatible:
loads/loadfollow the stdlib calling convention — migrating costs nothing
TOML version boundary: the 1.1 additions above are accepted by default. If your code relies on rejecting 1.0-invalid input (e.g.
13:37times), switch totoml_version="1.0"— the same files then raiseTOMLParseError.
Conformance & performance
Measured with toml-bench (toml-test 1.5.0 + CPython tomllib test data; speed = load/dump over 5000 iterations on one machine, tomlclass 0.2.0 — methodology in the benchmark baseline):
| Check | tomlclass 0.2.0 |
|---|---|
| toml-test 1.5.0 valid (187 files) | 187/187 — the only library with a perfect score |
| toml-test 1.5.0 TOML-1.1 manifest (548 files) | 548/548 |
| CPython tomllib test data | 12/12 valid, 50/50 invalid |
Speed (load / dump, 5000 iterations):
| Library | rtoml corpus | tomli corpus |
|---|---|---|
| rtoml 0.11 (Rust) | 0.72s / 0.16s | 0.52s / 0.33s |
| tomli 2.4 + tomli_w | 1.52s / 1.17s | 1.26s / 0.84s |
| tomllib (CPython) | 3.39s / — | 2.15s / — |
| tomlclass 0.2.0 | 4.26s / 3.80s | 3.12s / 2.22s |
| qtoml 0.3 | 7.78s / 2.97s | 6.35s / 1.97s |
| tomlkit 0.15 | 60.45s / 1.75s | 36.88s / 0.81s |
Lossless editing pays for bookkeeping: loads run ~2.5–2.8× tomli, dumps ~2.6–3.2× tomli_w — and 12–14× faster than tomlkit.
Installation## Installation
pip install tomlclass
Usage
Change one value, keep everything else
import tomlclass
tomlclass.update("pyproject.toml", {"project.version": "1.0.0"})
# only that line changed — comments, ordering and formatting all intact
Editing a TOML file (full control)
import tomlclass
doc = tomlclass.parse(text)
doc["project"]["version"] = "1.0.0"
doc["project"]["dependencies"].append("rich>=13.0") # spliced in place, comments kept
text = doc.dumps() # only touched lines change
Declarative config
from tomlclass import Config
class Server(Config):
"""
HTTP server settings.
host:
Address to bind.
port:
Port to listen on.
"""
host: str = "127.0.0.1"
port: int = 8000
server = Server.load("server.toml") # read + validate + merge defaults
server.port = 9000
server.save("server.toml") # only changed keys are written
Documentation
- Engine — parse, edit,
update(), comment API, errors - Config — schema declaration, template, load/save semantics, validation errors
- Comments — comment ownership, injection modes
- Examples — end-to-end scenarios
- Performance — measured baseline
Docs are also available in 简体中文.
Requirements
Python ≥ 3.10, no third-party dependencies.
License
Metadata
Release files for tomlclass 0.2.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| tomlclass-0.2.1.tar.gz | 269.9 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| tomlclass-0.2.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 313.2 kB
Release files / tomlclass-0.2.1.tar.gz
| Download URL | tomlclass-0.2.1.tar.gz |
|---|---|
| Size | 269.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
34e61ee7072d0d0c416ac95704c0f5519d6daf28c5370b99675130fe74b6bc1a
|
|
BLAKE2b-256 checksum How to use checksums |
7136128ddefa7a2718f6bf411031b84dac6db69ae5b2b62e3ce6092932a1b42d
|
| 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 6, 2026.
Transparency logRelease files / tomlclass-0.2.1-py3-none-any.whl
| Download URL | tomlclass-0.2.1-py3-none-any.whl |
|---|---|
| Size | 43.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1a5a1b311bc646c46b1f1443a87754f92f424c0d0166578af1295bc6b70f350d
|
|
BLAKE2b-256 checksum How to use checksums |
044db6c3fb6914107575cc37a71b7c61a31008e67ac5474ff6f55edd763df898
|
| 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 6, 2026.
Transparency log