Skip to content

perf: Python interpreter detection - #45

Merged
hisenb3rg merged 1 commit into
devfrom
fix/python-interpreter
Sep 16, 2026
Merged

hisenb3rg merged 1 commit into
devfrom
fix/python-interpreter

Conversation

@hisenb3rg

@hisenb3rg hisenb3rg commented Sep 16, 2026 •

Copy link
Copy Markdown
Collaborator

Summary

  • Step 0 ran all three interpreter probes (python3, py -3, python) in parallel and had to wait for every one to finish before picking <python>.
  • Now the probes run one at a time in that order and stop at the first whose output contains a current: line, so the common case is a single probe.
  • README aligned with the actual probe order (it listed py -3 first).

check_version.py and tests are unchanged.

Test plan

  • Run /pyro:render-spec on a spec on macOS/Linux: Step 0 issues only the python3 probe and reports it.
  • On a machine without python3 on PATH: falls through to py -3 / python.

🤖 Generated with Claude Code

@hisenb3rg hisenb3rg changed the title perf: Probe Python interpreters sequentially, stop at first success perf: Python interpreter detection Sep 16, 2026
Step 0 ran all three probes in parallel and waited for all of them
before picking an interpreter. It now tries python3, py -3 and python
in that order and stops at the first one that prints a current: line.
In the common case that is one probe instead of three. The README now
lists the same order.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@hisenb3rg
hisenb3rg force-pushed the fix/python-interpreter branch from dd9f8f4 to 7dd1414 Compare September 16, 2026 14:10
@hisenb3rg
hisenb3rg merged commit 26902e5 into dev Sep 16, 2026
6 checks passed
@hisenb3rg
hisenb3rg deleted the fix/python-interpreter branch September 16, 2026 14:20
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