Recordspypinumba0.67.0rc1numba.prange
Change the conditions
Current conditions
numba.prange @0.67.0rc1debian glibc · x64 · python 3.12 · pip · python
1 of 1 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 (1)
- Project observations
- 1 / 1
- Contract verifications
- 1 / 1
- Independent reporting peers
- 1
- Last recorded
- 2026-09-14
Dependency Health
Observed combinations and failure evidence for this release
First observed break
0.67.0rc1
windows · python@3.10
4 FAIL · stage: PROJECT_TEST
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| llvmlite | 0.49.0rc1 | CANDIDATE Correlated change; unproven combination | contract passed | 7 project-days |
| numpy | 2.5.1 | CANDIDATE Correlated change; unproven combination | contract passed | 7 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: 2 · unchanged at every release: 0
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.