Skip to content

Windows: Explicitly list versions with upper bound - #473

Merged
hugovk merged 1 commit into
python:mainfrom
hugovk:explicit-version-list
Nov 6, 2026
Merged

hugovk merged 1 commit into
python:mainfrom
hugovk:explicit-version-list

Conversation

@hugovk

@hugovk hugovk commented Nov 6, 2026

Copy link
Copy Markdown
Member

Follow on from #455.

I definitely found the change in that PR helped for the last releases: different wording like "(only up to 3.15)" is clearer than "(3.15 and earlier)", when we also have options like "(3.15 and later)".

I suggested somewhere about explicitly listing the versions, but we can't replace those like "(3.15 and later)" with "(3.15, 3.16)" because we'd have to remember to add 3.17 and so on.

But we can replace those like "(only up to 3.15)" with "(3.14, 3.15)" because it's a finite set, and it doesn't matter if we forget to remove 3.14 when it's no longer relevant.

Before:

  • Separate free-threaded outputs (3.15 and later)
  • Build with tail-calling support (3.15 and later)
  • Produce EXE/MSI installer (only up to 3.15)

After:

  • Separate free-threaded outputs (3.15 and later)
  • Build with tail-calling support (3.15 and later)
  • Produce EXE/MSI installer (3.14, 3.15)

@hugovk hugovk changed the title Explicitly list versions with upper bound Windows: Explicitly list versions with upper bound Nov 6, 2026
@hugovk
hugovk merged commit 8e89c17 into python:main Nov 6, 2026
20 checks passed
@hugovk
hugovk deleted the explicit-version-list branch November 6, 2026 20:31
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