ci: remove Python version comment from mac config
What changed, and why it matters
This commit simply removes two comment lines explaining why a Python package-installation flag is used in a macOS CI configuration file. No code, commands, or behavior change. It is not a security fix and has no security relevance.
No action needed; this is a non-functional documentation cleanup in CI configuration.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff deletes explanatory comments about Homebrew’s python@3.12 being externally managed (PEP 668) and the resulting need for --break-system-packages. The actual PIP_PACKAGES="--break-system-packages zmq" line remains unchanged. There are no functional changes to CI behavior, build scripts, or Bitcoin Core code.
Changed components
ci/test/00_setup_env_mac_native.shInspect captured patch +0 / −2
diff --git a/ci/test/00_setup_env_mac_native.sh b/ci/test/00_setup_env_mac_native.sh
index 41a3bc45..6e03f06e 100755
--- a/ci/test/00_setup_env_mac_native.sh
+++ b/ci/test/00_setup_env_mac_native.sh
@@ -6,8 +6,6 @@
export LC_ALL=C.UTF-8
-# Homebrew's python@3.12 is marked as externally managed (PEP 668).
-# Therefore, `--break-system-packages` is needed.
export CONTAINER_NAME="ci_mac_native" # macos does not use a container, but the env var is needed for logging
export PIP_PACKAGES="--break-system-packages zmq"
export GOAL="install deploy"
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.