Repository navigation
Test with Pint 0.26 - #207
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #207 +/- ##
=======================================
Coverage 91.37% 91.37%
=======================================
Files 6 6
Lines 232 232
=======================================
Hits 212 212
Misses 20 20 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
There was a problem hiding this comment.
Note
Copilot was unable to complete this review at the selected tier due to model policy or plan restrictions.
🟡 Changes recommended
Approval is blocked because the review evidence identifies unresolved compatibility and maintenance issues, including incomplete Pint-version coverage in CI and dependency range mismatches (unconstrained Pint in pixi.toml) alongside brittle doctests tied to exact repr output.
3 open issues
What changed in this PR
Updates dependency metadata, Pixi environments/lockfile, CI workflows, and doctest expectations to validate compatibility with Pint 0.26 (Closes #206).
Changes:
- Broaden Pint support in package metadata to include 0.26 (
pint>=0.25,<0.27) and refresh Pixi lock data. - Update Pixi environment definitions and CI matrices to run Pint 0.26-focused jobs.
- Adjust OpenMM-related doctest expected outputs to match Pint’s updated display behavior.
Key review notes to address before approval:
- CI coverage: restore at least one non-OpenMM Pixi environment run in
.github/workflows/ci.yaml(OpenMM is optional). - Lower-bound testing: either add Pint 0.25 to
.github/workflows/ci_pypi.yamlor bump the declared lower bound if 0.25 is no longer supported. - Doctest robustness: avoid asserting exact
repr()forQuantityinopenff/units/openmm.py(noted at lines ~165 and ~299); prefer explicit magnitude/unit assertions. - Pixi dependency alignment: constrain
pintinpixi.tomlto the supported range (currently unconstrained as"*").
| File | Summary |
|---|---|
pyproject.toml |
Updates declared Pint compatibility range to include 0.26 (>=0.25,<0.27). |
pixi.toml |
Updates Pixi environments/features for Pint 0.26; needs Pint version constraint aligned with pyproject.toml (currently "*"). |
pixi.lock |
Regenerates lockfile to resolve against Pint 0.26.x and related dependency updates. |
openff/units/openmm.py |
Updates doctest expected outputs; needs less brittle doctests than exact repr() matching (noted at ~165 and ~299). |
.github/workflows/ci.yaml |
Updates Pixi CI matrix to Pint 0.26 OpenMM environments; needs at least one non-OpenMM Pixi job retained. |
.github/workflows/ci_pypi.yaml |
Updates PyPI-install CI to Pint 0.26; needs Pint 0.25 coverage or a lower-bound bump to 0.26. |
This pull request requires changes.
Review effort: Balanced
j-wags
left a comment
There was a problem hiding this comment.
Thanks @mattwthompson - This looks good. I left one blocking and two nonblocking comments.
(not blocking) My claude review points out:
3. The reprs in docs/index.md are now out of date. The PR updates the two doctests in openmm.py to
Pint 0.26's new repr, Quantity(9.0, "angstrom"). But docs/index.md still shows <Quantity(...)> at
lines 38, 95, 111, 120 and 153, and the docs environment now builds with pint26. Users on 0.26 will
see output that doesn't match the docs.
| [pypi-options.dependency-overrides] | ||
| pint = ">=0.25,<0.27" | ||
|
|
There was a problem hiding this comment.
(not blocking) Just checking whether this section is needed - it seems to be a verbatim copy of the pint dep above
There was a problem hiding this comment.
I think it is, because the conda packages have a different pin
I will confirm this before merging
Co-authored-by: Jeff Wagner <jwagnerjpl@gmail.com>


Description
Closes #206
Todos
docteston docsAI disclosure