Repository navigation
BREAK: require excluded-python-versions to be an array - #734
Merged
Merged
Conversation
redeboer
force-pushed
the
enh/733-excluded-python-versions-array
branch
from
October 9, 2026 17:40
c23db19 to
20cc53e
Compare
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
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.
Closes #733
excluded-python-versionsin[tool.compwa.policy.python]must now be an array of known Python versions, such asexcluded-python-versions = ["3.14", "3.15"]. A string value like"3.14"or an unknown version like"3,14"is rejected, and the JSON schema lists the allowed versions.policy python --excluded-python-versionstakes one version per use and can be repeated, like--type-checker.policy migratesplits comma- or space-separated values of list-valued hook arguments into separate array items, so--excluded-python-versions=3.14,3.15becomes["3.14", "3.15"].Squash commit messages