Recordspypityping-inspectionfailure issue
Failure signature
PROJECT_TEST exit 1 ×1
E AssertionError: assert <str> == <str> · E · E - <token> · E + <token>
Evidence quality: complete · python/pytest · test-runner-diagnostic · First recorded: 2026-09-01 · Last seen: 2026-09-01
sha256:0d2f53766a98…
Where it was measured
PASS means the release recorded a passing observation at PROJECT_TEST 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-09-01 → 2026-09-01
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 0.4.2 → first passing release 0.4.4
Both trees resolved every dependency to the same version. Nothing here moved.
Dependency versions across releases
What each release of this package resolved its children to. A child whose version moved is listed first: that is where an upgrade changed something underneath you.
| Library | 0.4.4 | 0.4.2 |
|---|---|---|
| typing-extensions | 4.16.0 | 4.16.0 |
Moved: 0 · unchanged at every release: 1
An edge records that a resolver placed one release beside another on a real machine. It is not a claim that the two work together; that question is answered by samples and contracts, not by presence here.
Evidence gaps
- No failure domain was inferred for this failure.
Published answers for the affected releases
- typing-inspection 0.4.2: typing_inspection.introspection.inspect_annotation 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. HOWtyping_inspection.introspection.inspect_annotationpython MIT-0 · 2026-08-28