python-setuptools: build once and symlink

[cho-m]

Setuptools is pure python and an any wheel (https://pypi.org/project/setuptools/#setuptools-80.9.0-py3-none-any.whl) so it isn't Python version-specific.

Can also see from existing bottle, the contents of subdirectories are the same, e.g.

❯ diff --recursive $(brew --prefix python-setuptools)/lib/python3.12/ $(brew --prefix python-setuptools)/lib/python3.13/

❯ echo $?
0

---

For now, can keep all versions as we use Setuptools in some formulae we are unable to rebuild, e.g. versioned LLVM. Can re-consider in future.

Minor reduction in size from symlinks, though not that significant as only 4.3MB with 1 Python and 12.0MB with 3 Pythons.

[Copilot]

Pull Request Overview

This PR optimizes the python-setuptools formula by building setuptools once with the newest Python version and creating symlinks for other supported versions, rather than building separately for each Python version. This is possible because setuptools is a pure Python package distributed as a universal wheel.

Key Changes:

• Build setuptools once with Python 3.14 instead of building for each Python version (3.12, 3.13, 3.14)
• Create symlinks from other Python version site-packages to the built files
• Simplify the pythons helper method using filter_map

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull Request Overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated 2 comments.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull Request Overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated 4 comments.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[branchvincent]

nice!

[github-actions]

🤖 An automated task has requested bottles to be published to this PR.

Caution

Please do not push to this PR branch before the bottle commits have been pushed, as this results in a state that is difficult to recover from. If you need to resolve a merge conflict, please use a merge commit. Do not force-push to this PR branch.