CodeSampleX

Recordspypipytest

Change the conditions
Fixed
OSdebian glibc Package version8.4.1
Filter Runtimepython 3.12 Architecturex64 Package managerpip Execution contextpython libcglibc Clear filters

Current conditions

pytest @8.4.1debian glibc · x64 · python 3.12 · pip · python

2 of 2 passed

Verified — this network ran a contract at this coordinate.

there is a sample here, and our run of it at this coordinate came back clean (2)

Project observations
6 / 6
Contract verifications
2 / 2
Usage records
3
Independent reporting peers
1
Last recorded
2026-10-13

Exact records

This slice is down to its measured combinations — the environments below are exactly what ran.

Dependency Health

Observed combinations and failure evidence for this release

Changed 1 · Steady 4

Dependency changes observed: 1. No failure evidence is linked to these resolved trees yet.

Library Version Health Measured there Projects
packaging 26.3 CHANGED Version changed, no linked failure contract passed 2 project-days
colorama 0.4.6 PASS All observations passed contract passed 2 project-days
iniconfig 2.3.0 PASS All observations passed contract passed 2 project-days
pluggy 1.6.0 PASS All observations passed contract passed 2 project-days
pygments 2.21.0 PASS All observations passed contract passed 2 project-days

The measured column is about each dependency's own release, not about the pair. A resolver placing two releases side by side is not evidence that they work together.

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.

Moved: 1 · unchanged at every release: 4

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.