Description
It may be a good time to review the current project dependencies overall, both to keep them up to date and to re-evaluate version constraints where appropriate.
At the moment, most runtime dependencies use version ranges, but some are still strict-pinned, such as:
MarkupSafe==3.0.3rich==14.2.0
A broader dependency review could help determine whether these exact pins are still required and whether some constraints could be safely modernized.
Possible goals for this review:
- Update outdated dependencies where relevant
- Reassess strict pins versus compatible version ranges
- Reduce dependency resolution conflicts for users
- Improve compatibility with modern Python ecosystems and tooling
- Keep CI coverage aligned with supported versions
If some constraints are intentionally strict because of regressions or known incompatibilities, documenting that reasoning would also be very helpful.
Description
It may be a good time to review the current project dependencies overall, both to keep them up to date and to re-evaluate version constraints where appropriate.
At the moment, most runtime dependencies use version ranges, but some are still strict-pinned, such as:
MarkupSafe==3.0.3rich==14.2.0A broader dependency review could help determine whether these exact pins are still required and whether some constraints could be safely modernized.
Possible goals for this review:
If some constraints are intentionally strict because of regressions or known incompatibilities, documenting that reasoning would also be very helpful.