Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 74.09%. Comparing base (b308592) to head (821763c).
Report is 4 commits behind head on main.

@@            Coverage Diff             @@
##             main    #1908      +/-   ##
==========================================
- Coverage   74.10%   74.09%   -0.01%     
==========================================
  Files         444      444              
  Lines       55514    55514              
  Branches     9128     9126       -2     
==========================================
- Hits        41138    41135       -3     
- Misses      11285    11287       +2     
- Partials     3091     3092       +1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

This kind of PR makes me wonder when it makes sense to have a requirements.txt for developer dependencies.

I briefly started in this direction, but was dissuaded by a bunch of sources that suggested that requirements.txt is old and busted and that we ought to be using a pyproject.toml instead, and then thinking about the headache of doing that with something that isn't a Python project managed by one of the typical Python packaging systems.

My take is that requirements.txt is old and busted for use cases where you need to have consistent versioning, for library or application dependencies primarily. I agree pyproject.toml is not what we want. I think using requirements.txt for our case is more than appropriate and I'd be shocked if [uv] pip install -r stopped working any time in the near future. 🤷‍♂️

I don't have strong opinions, but believe that having a sufficiently spread-out test matrix on the CI should be adequate? (I'm not sure that all of us have to have the exact same toolchain.) As long as we test 3-4 versions plus bleeding edge on critical infrastructure we should be good. We mostly are already doing this ... the only one missing is the recent additional dependency on doxygen (which could be made optional if users don't care about CLib).

The idea for requirements.txt or similar would mostly help in defining package versions for CI. Instead of having to change every job when we need to change a version or add/remove a dependency, it'd be just one (or a few) file(s) that need to change.