Recordspypisqlalchemy2.0.51sqlalchemy.Integer
Change the conditions
Current conditions
sqlalchemy.Integer @2.0.51ubuntu glibc · x64 · python 3.12 · pip
2 of 2 passed
Observed — real project builds reported from this coordinate.
there is a sample here, and nothing of ours has run it at this coordinate yet (1)
- Project observations
- 2 / 2
- Contract verifications
- nothing at this coordinate
- Independent reporting peers
- 2
- Last recorded
- 2026-08-31
Evidence you can open
Dependency Health
Observed combinations and failure evidence for this release
Observed problems 3 ·
Steady 0
First observed break
2.0.51
windows · python@3.10
4 FAIL · stage: PROJECT_TEST
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| greenlet | 3.5.4 | FAIL Linked failure observed on this release | contract passed | 6 project-days |
| greenlet | 3.5.5 | FAIL Linked failure observed on this release | contract passed | 8 project-days |
| typing-extensions | 4.16.0 | FAIL Linked failure observed on this release | contract passed | 14 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.
Recent failure clusters
-
observed UNKNOWN exit 1 Evidence gap ×1 2.0.51 os=linux · runtime=python@3.12 sha256:03cd650ce90c…Traceback (most recent call last): · File <str>, line 9, in <module> · from sqlalchemy import select · ModuleNotFoundError: No module named <str>python3 · unclassified-diagnostic · outer python3 · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-31 · Last seen: 2026-08-31Diagnostic re-verification candidate