chore!: eradicate all Python — total ban, no exceptions#279
Open
hyperpolymath wants to merge 1 commit into
Open
chore!: eradicate all Python — total ban, no exceptions#279hyperpolymath wants to merge 1 commit into
hyperpolymath wants to merge 1 commit into
Conversation
The org Python ban is now absolute (no SaltStack-style carve-outs). This removes every Python site in hypatia and replaces each with a faithful, verified Rust port: scripts/bench-tools/ (zero-dep, standalone crate; was on the #272 lineage — vendored here so this PR is self-contained) - check-bench-regression <- scripts/check-bench-regression.py - update-bench-baselines <- scripts/update-bench-baselines.py scripts/ci-tools/ (standalone crate) - validate-panll-harness <- inline python3+jsonschema in build-gossamer-gui.yml (TOML -> JSON-Schema Draft 2020-12) - check-k9iser-paths <- inline python3 in ci.yml Callers rewired: tests.yml (x2), build-gossamer-gui.yml (drops the `pip install jsonschema` step entirely), ci.yml, benchmarks README. Exemptions revoked (the ban has no exceptions): .hypatia-ignore block, .hypatia-exemptions.md rows, .hypatia-baseline.json entries for the two .py files. Verification: all four Rust bins build clean (cargo 1.95); functionally smoke-tested against the real k9iser.toml (5 src/3 constraint) and the real panll.harness.toml vs the live panll-harness/v2 schema (both pass). Tracked .py files: 2 -> 0. Unblocks the `Check for Python (non-SaltStack)` governance gate that was failing unrelated PRs (e.g. #270, a pure just-version pin) as inherited baseline rot rather than a per-PR defect. Follow-up (separate, standards-level): the governance rule itself should stop honouring `banned_language_file` exemptions now the ban is total. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
The org Python ban is now total, with no exceptions (no SaltStack-style carve-outs). This removes every Python site in hypatia and replaces each with a faithful, verified Rust port.
Also unblocks the
governance / Language / package anti-pattern policy → Check for Python (non-SaltStack)gate that was failing unrelated PRs (e.g. #270, a purejustversion pin) as inherited baseline rot — not per-PR defects.What
scripts/check-bench-regression.pyscripts/bench-tools→check-bench-regressionscripts/update-bench-baselines.pyscripts/bench-tools→update-bench-baselinespython3+jsonschemainbuild-gossamer-gui.ymlscripts/ci-tools→validate-panll-harness(TOML → JSON-Schema Draft 2020-12)python3inci.ymlscripts/ci-tools→check-k9iser-pathsbench-toolsis zero-dependency (was authored on the fix(reconcile): --verify no longer crashes JSON-encoding its result #272 lineage; vendored here so this PR is self-contained and order-independent).build-gossamer-gui.ymlloses itspip install jsonschemastep entirely.tests.yml(×2),build-gossamer-gui.yml,ci.yml, benchmarks README..hypatia-ignoreblock,.hypatia-exemptions.mdrows,.hypatia-baseline.jsonentries.Verification
check-k9iser-paths: realk9iser.toml→OK … 5 source(s), 3 constraint(s), exit 0.validate-panll-harness: realpanll.harness.tomlvs the live panll-harness/v2 schema →OK …, exit 0..pyfiles: 2 → 0.Follow-up (separate, standards-level)
The governance rule itself should stop honouring
banned_language_fileexemptions now the ban is total — likely an estate-wide standards change, out of scope here.🤖 Generated with Claude Code