Skip to content

👷 ci(brew): add missing Homebrew Python versions and fix discovery#3066

Merged
gaborbernat merged 4 commits into
pypa:mainfrom
gaborbernat:add-brew-ci-versions
Feb 23, 2026
Merged

👷 ci(brew): add missing Homebrew Python versions and fix discovery#3066
gaborbernat merged 4 commits into
pypa:mainfrom
gaborbernat:add-brew-ci-versions

Conversation

@gaborbernat

@gaborbernat gaborbernat commented Feb 23, 2026

Copy link
Copy Markdown
Contributor

The macOS CI matrix only tested Homebrew-installed Python 3.9 through 3.11, but Homebrew now ships python@3.12, python@3.13, and python@3.14. This gap means virtualenv's Homebrew-specific code path (CPython3macOsBrew) wasn't being validated against the versions most users actually install today.

Additionally, the existing brew jobs were broken — they set TOX_DISCOVER to point at the brew interpreter, but tox-uv ignores that variable entirely. The tox test environments were silently using the actions/setup-python interpreter instead of the brew one, defeating the purpose of these matrix entries. 🔧 Switching to UV_PYTHON ensures tox-uv actually creates the test environment with the Homebrew Python.

@gaborbernat gaborbernat changed the title Add brew CI tests for Python 3.12, 3.13, 3.14 👷 ci(brew): add Homebrew Python 3.12, 3.13, 3.14 to matrix Feb 23, 2026
@gaborbernat gaborbernat changed the title 👷 ci(brew): add Homebrew Python 3.12, 3.13, 3.14 to matrix 👷 ci(brew): add missing Homebrew Python versions and fix discovery Feb 23, 2026
@gaborbernat gaborbernat enabled auto-merge (squash) February 23, 2026 13:31
The gh CLI requires authentication via GH_TOKEN to access the GitHub
API in Actions workflows. Without it the nushell release download
fails with exit code 4 on all Windows matrix entries.
The chocolatey nushell package installation is unreliable due to CDN
timeouts. The gh release download approach works but GITHUB_PATH
additions don't propagate into tox test environments. Copying nu.exe
directly to the chocolatey bin directory (already on system PATH)
ensures the nushell activation tests can find the binary.
The nushell release zip extracts files flat (no subdirectory), so nu.exe
is directly under the extraction output directory.
@gaborbernat gaborbernat merged commit c22b548 into pypa:main Feb 23, 2026
109 of 110 checks passed
This was referenced Mar 16, 2026
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.

1 participant