Skip to content

Fix Python 3.12 execution through the current bot alias - #303

Draft
aberson wants to merge 1 commit into
masterfrom
fix/current-alias-python312
Draft

aberson wants to merge 1 commit into
masterfrom
fix/current-alias-python312

Conversation

@aberson

@aberson aberson commented Sep 28, 2026 •

Copy link
Copy Markdown
Owner

Running python -m bots.current.runner --help on Python 3.12 crashes because the alias spec loses its source origin. runpy sets sys.argv[0] to None, then argparse fails. Preserve the target spec's origin and location flag so alias execution receives the real source path.

Adds a subprocess regression for the source-file contract, which also detects the defect on Python 3.14 where argparse masks the original symptom. Existing import-identity and CLI tests remain intact. No dependency, supported-Python, or CI configuration changes.

Validation:

  • Original CLI failure reproduced on Windows and Linux Python 3.12 before the fix.
  • New regression confirmed failing before the source edit.
  • All 9 alias tests pass on Windows Python 3.12/3.14 and Linux Python 3.12.
  • On the development branch containing this same patch: 2,024 Python tests passed (3 skipped, 1 deselected), 228 frontend tests passed (6 skipped), ruff and strict mypy passed.
  • Independent correctness, bugs, security, tests, and style review completed; no blocking findings.
  • Hosted Ubuntu 22.04 / Python 3.12 CI passed: 1,953 tests passed, 22 skipped, 1 deselected; ruff and strict mypy passed (run).

This PR contains only the two-file CI repair, cherry-picked onto master. Hosted CI verifies the master-based combination separately from the development branch.

aberson added a commit that referenced this pull request Oct 4, 2026
…kfill Issue fields

/repo-sync on documentation/plans/evolve-operational-hardening-plan.md.
Pre-flight: target repo aberson/Alpha4Gate, default branch master, both
prerequisite gates evidenced (plan-review autofix 07017da; plan-wrap passed
2026-09-19; nine redline decisions P-1..P-9 recorded). No cross-plan
collisions — no Phase EH issues existed.

Created 1 umbrella + 10 step issues, all rich bodies (10/10 steps rich on the
richness check). Backfilled all ten **Issue:** fields; repo-sync's verification
grep for blank/TBD values returns empty.

Two corrections made during the sync:
- The plan predicted issue numbering would start at #303, but #303 and #304
  were taken by pull requests in the interim. Actual range is #305 + #306-#315;
  the stale prediction is corrected in the plan and in the umbrella body.
- Step EH.10's issue body initially carried a truncated Depends-on list. The
  plan's §7 line names seven predecessors (EH.1, EH.2, EH.4, EH.5, EH.6, EH.7,
  EH.9); the issue now matches it.

EH.5 is the one frontend-touching step. Its plan Flags line carries no --ui, so
repo-sync added it per the UI-bundle dial and made dashboard evidence part of
acceptance.

Also corrects the Phase EI index row in the master plan: plan-review and
plan-wrap both passed 2026-09-02, but EI has never been redlined, so it needs
/plan-redline before any build. EI is sequenced after EH per EH §6 D-8 — both
edit scripts/evolve.py and must be built one at a time.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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