Test supported Python versions in CI - #349
Merged
Merged
Conversation
Contributor
|
uriahf
marked this pull request as ready for review
August 20, 2026 19:17
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Audit result
Python 3.10, 3.11, 3.12, and 3.13 all passed lint, format,
ty, build, and the full test suite in the probe run.Python 3.14 was also probed, but the current locked dev environment did not get past dependency installation during the run. Rather than mix dependency upgrades into this PR, 3.14 support is deferred to the dependency-refresh step.
Scope
CI compatibility coverage only. No runtime dependency changes, API changes, statistical changes, or source refactoring.
Follow-up audit findings
plotlyandpolarstateare duplicated in the dev dependency group even though they are runtime dependencies<6while current stable Plotly is 6.xpl.count()Those should be handled incrementally in separate PRs.