Skip to content

Compatibility workflow: skip Python versions not allowed by requires-python - #54

Closed
seb5g wants to merge 1 commit into
5.3.xfrom
fix/compat-requires-python
Closed

seb5g wants to merge 1 commit into
5.3.xfrom
fix/compat-requires-python

Conversation

@seb5g

@seb5g seb5g commented Oct 12, 2026

Copy link
Copy Markdown
Contributor

Before: the shared compatibility workflow always tests Python 3.10, so a plugin with requires-python = ">=3.11" (e.g. mockexamples) fails with "requires a different Python: 3.10 not in '>=3.11'".

After: a first step reads requires-python from the plugin's pyproject.toml and the install and test steps are skipped (job green) for the Python versions it excludes. Plugins that support 3.10 are unchanged.

How: packaging.specifiers on the version of the running interpreter, result in a step output used by if: on the next steps. The logic was run locally against a >=3.11 pyproject; the workflow itself is only exercised by CI once merged (plugins call it at @5.3.x).

🤖 Generated with Claude Code

https://claude.ai/code/session_01Tdiso1u1ZhikSutj2Qs5Cg


Generated by Claude Code

@seb5g seb5g closed this Oct 12, 2026
@seb5g
seb5g deleted the fix/compat-requires-python branch October 12, 2026 19:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants