Recordspypitomlifailure issue
Failure signature
PROJECT_PROCESS Evidence gap ×1
Evidence quality: legacy-evidence-incomplete · First recorded: 2026-08-17 · Last seen: 2026-08-17
tomli
Where it was measured
PASS means the release recorded a passing observation at PROJECT_PROCESS and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.
- 2.4.1 FAIL
Where it reproduced
- os=windows · runtime=python@3.10 ×1 2026-08-17 → 2026-08-17
Nearest known PASS/FAIL boundaries
No release either side of this failure recorded a passing observation at this stage, so where it starts and stops is not established.
Evidence gaps
- The evidence for this failure was not preserved, so it has no established cause. Its stored hash is provenance, not an identity.
- No release in this window recorded a passing observation at PROJECT_PROCESS.
- No failure domain was inferred for this failure.
Published answers for the affected releases
- tomli 2.4.1: Read TOML across Python versions where stdlib tomllib is absent (<3.11) versus present (>=3.11) without tripping on binary-only load, str-only loads, positional parameters, and missing dump methods This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWtomli.loadtomli.loadstomli.TOMLDecodeErrorpython MIT-0 · 2026-08-15