Recordspypipycparserfailure issue
Failure signature
PROJECT_PROCESS Evidence gap ×1
Evidence quality: legacy-evidence-incomplete · First recorded: 2026-08-17 · Last seen: 2026-08-17
pycparser.c_parser pycparser.plyparser.ParseError
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.
Where it reproduced
- os=windows · runtime=python@3.10 ×1 2026-08-17 → 2026-08-17
Nearest known PASS/FAIL boundaries
The two adjacent releases the verdict changes across. Releases nothing measured do not close the gap; they are counted instead.
-
Last failing release 2.22 → first passing release 3.0
Both trees resolved every dependency to the same version. Nothing here moved.
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 failure domain was inferred for this failure.
Published answers for the affected releases
- pycparser 2.22: Parse C99 source declarations into a FileAST hierarchy, manage typedef scoping with isolated state per invocation, and track source coordinates with CParser.parse in pycparser 2.22. 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. HOWpycparser.c_parser.CParser.parsepython MIT-0 · 2026-08-17
- pycparser 2.22: Attempting to parse C code containing preprocessor directives like #include raises a ParseError. 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. HOWpycparser.c_parser.CParserpycparser.plyparser.ParseErrorpython MIT-0 · 2026-08-17