gitgrip 1.5.1__tar.gz → 2.0.0a2__tar.gz

gitgrip-2.0.0a2/PKG-INFO

@@ -0,0 +1,116 @@
+Metadata-Version: 2.4
+Name: gitgrip
+Version: 2.0.0a2
+Summary: Workspace layer for multi-repo work: workspaces, isolated lanes, and one grouped review per slice
+Requires-Python: >=3.11
+Description-Content-Type: text/markdown
+Requires-Dist: typer>=0.9
+Requires-Dist: tomli_w>=1.0
+Requires-Dist: pyyaml>=6.0
+Requires-Dist: toml>=0.10
+Requires-Dist: jsonschema>=4.18
+Provides-Extra: dev
+Requires-Dist: pytest>=8.0; extra == "dev"
+Requires-Dist: ruff>=0.4; extra == "dev"
+
+# gr2
+
+**gr2 is the workspace layer for multi-repo work.** One repository is just git; when a change spans repositories — a feature slice, a release, several agents touching several repos — gr2 gives you a workspace over them, isolated lanes to work in, and one grouped review/PR set for the slice. It is the Python successor to the Rust `gr` (1.x, called gr1 below); both ship from this repository, and `gr2` is the command for the workspace and the slice.
+
+## Install
+
+```bash
+python3 -m venv ~/gr2-venv && source ~/gr2-venv/bin/activate
+pip install --pre gitgrip        # the PyPI package is "gitgrip"; the command is "gr2"
+gr2 --version
+```
+
+`--pre` is required while 2.x is an alpha — without it pip installs 1.5.1, which is gr1. To run unreleased development code instead, install from a checkout: `pip install -e gr2/` from the repository root.
+
+The Rust `gr` (gr1, 1.x) installs with `brew install synapt-dev/tap/gitgrip` or `cargo install gitgrip`. The two do not collide; you can have both installed.
+
+## First five minutes
+
+Every command below was run, in this order, in a clean virtualenv against a throwaway workspace of two repositories. Put two clones side by side in one folder, say `~/ws/repo-a` and `~/ws/repo-b`.
+
+```bash
+cd ~/ws
+gr2 workspace init ~/ws                 # scans the folder; writes .grip/workspace_spec.toml
+gr2 workspace materialize ~/ws --yes    # builds the .grip layout and a default unit
+gr2 workspace status ~/ws               # what kind of workspace this is
+gr2 store init ~/ws                     # the workspace snapshot store (needed before review)
+```
+
+A **unit** is one worker — you, or one agent — and `default` is created for you. A **lane** is one piece of work spanning repos, with its own clones, so two lanes never step on each other:
+
+```bash
+gr2 lane create ~/ws default feat-x --repos repo-a,repo-b --branch feat/x
+gr2 lane enter  ~/ws default feat-x --actor human:you
+```
+
+Both commands print, per repo, the absolute directory you work in:
+
+```
+repo-a: ~/ws/.grip/state/lanes/default/feat-x/repos/repo-a
+repo-b: ~/ws/.grip/state/lanes/default/feat-x/repos/repo-b
+```
+
+Edit there — not in your original clones. Stage and commit across the lane's repos:
+
+```bash
+gr2 add . --repo-path ~/ws/.grip/state/lanes/default/feat-x/repos/repo-a
+gr2 commit -m "my change" --workspace-root ~/ws --owner-unit default
+```
+
+`commit` with the lane flags commits every lane repo that has staged changes and names the repos it skipped. If every repo was skipped it exits non-zero with one sentence naming where it looked — and, when it can see them, where your staged changes actually are. Run one command across every lane repo, then turn the lane into one reviewable object:
+
+```bash
+gr2 exec run ~/ws default --actor human:you -- pytest -q   # one command, every lane repo
+gr2 review create-project ~/ws default feat-x              # prints gr:<sha>: one object to review
+gr2 lane current ~/ws default                              # where am I?
+gr2 lane exit ~/ws default --actor human:you
+```
+
+`exec run` and `lane exit` require `--actor`. Every group and verb takes `--help`; `gr2 --help` lists them all.
+
+## What works today, and what is not there yet
+
+Alpha 2 is a working local workspace layer. Verified by running the walk above:
+
+- `workspace` (init, materialize, status, migrate-gr1 from a gr1 gripspace), `lane` (create, enter, exit, current, lease), `store` (init, snapshot, log, diff, checkout), `exec run`, `repo status`, `sync status`, `review create-project`.
+- Lanes are independent clones: two lanes, or two agents, never share refs, an index, or a working tree.
+- A lane commit that commits nothing anywhere refuses loudly instead of reporting success.
+
+Not there yet:
+
+- The full walk with **remote** PRs (`gr2 push`, `gr2 pr create`) is documented in `--help` but was not exercised in a clean environment for this README; treat those two as alpha.
+- `gr2 --help` and some verb output still say "prototype" in places; the wording is being cleaned up as verbs land.
+- The Rust `gr` (gr1) still owns `spawn`, `fleet`, and `manifest` until their gr2 ports land. Everything else — workspace sync, lanes, the multi-repo slice, its review — is gr2's job; if a verb is missing or wrong there, that is a bug worth reporting, not a reason to reach for gr1.
+
+## Commands
+
+| Group | Verbs |
+|---|---|
+| `workspace` | init, init-from-topology, materialize, status, convert-clone, detect-gr1, migrate-gr1, migrate-lane-state, bootstrap-gr1 |
+| `spec` | show, validate |
+| `lane` | create, enter, exit, current, resolve, bind, lease |
+| (top level) | branch, add, commit, push, prune |
+| `sync` | status, run |
+| `pr` | create, status, checks, merge |
+| `review` | open, close, checkout-pr, run, requirements, bind, verify, rebind, create-project |
+| `exec` | status, run |
+| `repo` | status, hooks, hook-run, projection-run |
+| `store` | init, snapshot, log, diff, checkout |
+| `target`, `config`, `plan`, `apply` | stored PR target; config overlays; show/apply the materialization plan |
+
+## Overlay substrate
+
+gr2 also carries the config-overlay substrate (capture, compose, and materialize configuration layers over a workspace): see [docs/OVERLAY-SUBSTRATE.md](docs/OVERLAY-SUBSTRATE.md).
+
+## Development
+
+```bash
+pip install -e "gr2[dev]"    # from the repository root
+cd gr2 && pytest             # the gr2 suite (tests + overlay tests)
+cd gr2 && ruff check .       # lint, same config as CI
+```

gitgrip-2.0.0a2/README.md

@@ -0,0 +1,101 @@
+# gr2
+
+**gr2 is the workspace layer for multi-repo work.** One repository is just git; when a change spans repositories — a feature slice, a release, several agents touching several repos — gr2 gives you a workspace over them, isolated lanes to work in, and one grouped review/PR set for the slice. It is the Python successor to the Rust `gr` (1.x, called gr1 below); both ship from this repository, and `gr2` is the command for the workspace and the slice.
+
+## Install
+
+```bash
+python3 -m venv ~/gr2-venv && source ~/gr2-venv/bin/activate
+pip install --pre gitgrip        # the PyPI package is "gitgrip"; the command is "gr2"
+gr2 --version
+```
+
+`--pre` is required while 2.x is an alpha — without it pip installs 1.5.1, which is gr1. To run unreleased development code instead, install from a checkout: `pip install -e gr2/` from the repository root.
+
+The Rust `gr` (gr1, 1.x) installs with `brew install synapt-dev/tap/gitgrip` or `cargo install gitgrip`. The two do not collide; you can have both installed.
+
+## First five minutes
+
+Every command below was run, in this order, in a clean virtualenv against a throwaway workspace of two repositories. Put two clones side by side in one folder, say `~/ws/repo-a` and `~/ws/repo-b`.
+
+```bash
+cd ~/ws
+gr2 workspace init ~/ws                 # scans the folder; writes .grip/workspace_spec.toml
+gr2 workspace materialize ~/ws --yes    # builds the .grip layout and a default unit
+gr2 workspace status ~/ws               # what kind of workspace this is
+gr2 store init ~/ws                     # the workspace snapshot store (needed before review)
+```
+
+A **unit** is one worker — you, or one agent — and `default` is created for you. A **lane** is one piece of work spanning repos, with its own clones, so two lanes never step on each other:
+
+```bash
+gr2 lane create ~/ws default feat-x --repos repo-a,repo-b --branch feat/x
+gr2 lane enter  ~/ws default feat-x --actor human:you
+```
+
+Both commands print, per repo, the absolute directory you work in:
+
+```
+repo-a: ~/ws/.grip/state/lanes/default/feat-x/repos/repo-a
+repo-b: ~/ws/.grip/state/lanes/default/feat-x/repos/repo-b
+```
+
+Edit there — not in your original clones. Stage and commit across the lane's repos:
+
+```bash
+gr2 add . --repo-path ~/ws/.grip/state/lanes/default/feat-x/repos/repo-a
+gr2 commit -m "my change" --workspace-root ~/ws --owner-unit default
+```
+
+`commit` with the lane flags commits every lane repo that has staged changes and names the repos it skipped. If every repo was skipped it exits non-zero with one sentence naming where it looked — and, when it can see them, where your staged changes actually are. Run one command across every lane repo, then turn the lane into one reviewable object:
+
+```bash
+gr2 exec run ~/ws default --actor human:you -- pytest -q   # one command, every lane repo
+gr2 review create-project ~/ws default feat-x              # prints gr:<sha>: one object to review
+gr2 lane current ~/ws default                              # where am I?
+gr2 lane exit ~/ws default --actor human:you
+```
+
+`exec run` and `lane exit` require `--actor`. Every group and verb takes `--help`; `gr2 --help` lists them all.
+
+## What works today, and what is not there yet
+
+Alpha 2 is a working local workspace layer. Verified by running the walk above:
+
+- `workspace` (init, materialize, status, migrate-gr1 from a gr1 gripspace), `lane` (create, enter, exit, current, lease), `store` (init, snapshot, log, diff, checkout), `exec run`, `repo status`, `sync status`, `review create-project`.
+- Lanes are independent clones: two lanes, or two agents, never share refs, an index, or a working tree.
+- A lane commit that commits nothing anywhere refuses loudly instead of reporting success.
+
+Not there yet:
+
+- The full walk with **remote** PRs (`gr2 push`, `gr2 pr create`) is documented in `--help` but was not exercised in a clean environment for this README; treat those two as alpha.
+- `gr2 --help` and some verb output still say "prototype" in places; the wording is being cleaned up as verbs land.
+- The Rust `gr` (gr1) still owns `spawn`, `fleet`, and `manifest` until their gr2 ports land. Everything else — workspace sync, lanes, the multi-repo slice, its review — is gr2's job; if a verb is missing or wrong there, that is a bug worth reporting, not a reason to reach for gr1.
+
+## Commands
+
+| Group | Verbs |
+|---|---|
+| `workspace` | init, init-from-topology, materialize, status, convert-clone, detect-gr1, migrate-gr1, migrate-lane-state, bootstrap-gr1 |
+| `spec` | show, validate |
+| `lane` | create, enter, exit, current, resolve, bind, lease |
+| (top level) | branch, add, commit, push, prune |
+| `sync` | status, run |
+| `pr` | create, status, checks, merge |
+| `review` | open, close, checkout-pr, run, requirements, bind, verify, rebind, create-project |
+| `exec` | status, run |
+| `repo` | status, hooks, hook-run, projection-run |
+| `store` | init, snapshot, log, diff, checkout |
+| `target`, `config`, `plan`, `apply` | stored PR target; config overlays; show/apply the materialization plan |
+
+## Overlay substrate
+
+gr2 also carries the config-overlay substrate (capture, compose, and materialize configuration layers over a workspace): see [docs/OVERLAY-SUBSTRATE.md](docs/OVERLAY-SUBSTRATE.md).
+
+## Development
+
+```bash
+pip install -e "gr2[dev]"    # from the repository root
+cd gr2 && pytest             # the gr2 suite (tests + overlay tests)
+cd gr2 && ruff check .       # lint, same config as CI
+```

gitgrip-2.0.0a2/gitgrip.egg-info/PKG-INFO

@@ -0,0 +1,116 @@
+Metadata-Version: 2.4
+Name: gitgrip
+Version: 2.0.0a2
+Summary: Workspace layer for multi-repo work: workspaces, isolated lanes, and one grouped review per slice
+Requires-Python: >=3.11
+Description-Content-Type: text/markdown
+Requires-Dist: typer>=0.9
+Requires-Dist: tomli_w>=1.0
+Requires-Dist: pyyaml>=6.0
+Requires-Dist: toml>=0.10
+Requires-Dist: jsonschema>=4.18
+Provides-Extra: dev
+Requires-Dist: pytest>=8.0; extra == "dev"
+Requires-Dist: ruff>=0.4; extra == "dev"
+
+# gr2
+
+**gr2 is the workspace layer for multi-repo work.** One repository is just git; when a change spans repositories — a feature slice, a release, several agents touching several repos — gr2 gives you a workspace over them, isolated lanes to work in, and one grouped review/PR set for the slice. It is the Python successor to the Rust `gr` (1.x, called gr1 below); both ship from this repository, and `gr2` is the command for the workspace and the slice.
+
+## Install
+
+```bash
+python3 -m venv ~/gr2-venv && source ~/gr2-venv/bin/activate
+pip install --pre gitgrip        # the PyPI package is "gitgrip"; the command is "gr2"
+gr2 --version
+```
+
+`--pre` is required while 2.x is an alpha — without it pip installs 1.5.1, which is gr1. To run unreleased development code instead, install from a checkout: `pip install -e gr2/` from the repository root.
+
+The Rust `gr` (gr1, 1.x) installs with `brew install synapt-dev/tap/gitgrip` or `cargo install gitgrip`. The two do not collide; you can have both installed.
+
+## First five minutes
+
+Every command below was run, in this order, in a clean virtualenv against a throwaway workspace of two repositories. Put two clones side by side in one folder, say `~/ws/repo-a` and `~/ws/repo-b`.
+
+```bash
+cd ~/ws
+gr2 workspace init ~/ws                 # scans the folder; writes .grip/workspace_spec.toml
+gr2 workspace materialize ~/ws --yes    # builds the .grip layout and a default unit
+gr2 workspace status ~/ws               # what kind of workspace this is
+gr2 store init ~/ws                     # the workspace snapshot store (needed before review)
+```
+
+A **unit** is one worker — you, or one agent — and `default` is created for you. A **lane** is one piece of work spanning repos, with its own clones, so two lanes never step on each other:
+
+```bash
+gr2 lane create ~/ws default feat-x --repos repo-a,repo-b --branch feat/x
+gr2 lane enter  ~/ws default feat-x --actor human:you
+```
+
+Both commands print, per repo, the absolute directory you work in:
+
+```
+repo-a: ~/ws/.grip/state/lanes/default/feat-x/repos/repo-a
+repo-b: ~/ws/.grip/state/lanes/default/feat-x/repos/repo-b
+```
+
+Edit there — not in your original clones. Stage and commit across the lane's repos:
+
+```bash
+gr2 add . --repo-path ~/ws/.grip/state/lanes/default/feat-x/repos/repo-a
+gr2 commit -m "my change" --workspace-root ~/ws --owner-unit default
+```
+
+`commit` with the lane flags commits every lane repo that has staged changes and names the repos it skipped. If every repo was skipped it exits non-zero with one sentence naming where it looked — and, when it can see them, where your staged changes actually are. Run one command across every lane repo, then turn the lane into one reviewable object:
+
+```bash
+gr2 exec run ~/ws default --actor human:you -- pytest -q   # one command, every lane repo
+gr2 review create-project ~/ws default feat-x              # prints gr:<sha>: one object to review
+gr2 lane current ~/ws default                              # where am I?
+gr2 lane exit ~/ws default --actor human:you
+```
+
+`exec run` and `lane exit` require `--actor`. Every group and verb takes `--help`; `gr2 --help` lists them all.
+
+## What works today, and what is not there yet
+
+Alpha 2 is a working local workspace layer. Verified by running the walk above:
+
+- `workspace` (init, materialize, status, migrate-gr1 from a gr1 gripspace), `lane` (create, enter, exit, current, lease), `store` (init, snapshot, log, diff, checkout), `exec run`, `repo status`, `sync status`, `review create-project`.
+- Lanes are independent clones: two lanes, or two agents, never share refs, an index, or a working tree.
+- A lane commit that commits nothing anywhere refuses loudly instead of reporting success.
+
+Not there yet:
+
+- The full walk with **remote** PRs (`gr2 push`, `gr2 pr create`) is documented in `--help` but was not exercised in a clean environment for this README; treat those two as alpha.
+- `gr2 --help` and some verb output still say "prototype" in places; the wording is being cleaned up as verbs land.
+- The Rust `gr` (gr1) still owns `spawn`, `fleet`, and `manifest` until their gr2 ports land. Everything else — workspace sync, lanes, the multi-repo slice, its review — is gr2's job; if a verb is missing or wrong there, that is a bug worth reporting, not a reason to reach for gr1.
+
+## Commands
+
+| Group | Verbs |
+|---|---|
+| `workspace` | init, init-from-topology, materialize, status, convert-clone, detect-gr1, migrate-gr1, migrate-lane-state, bootstrap-gr1 |
+| `spec` | show, validate |
+| `lane` | create, enter, exit, current, resolve, bind, lease |
+| (top level) | branch, add, commit, push, prune |
+| `sync` | status, run |
+| `pr` | create, status, checks, merge |
+| `review` | open, close, checkout-pr, run, requirements, bind, verify, rebind, create-project |
+| `exec` | status, run |
+| `repo` | status, hooks, hook-run, projection-run |
+| `store` | init, snapshot, log, diff, checkout |
+| `target`, `config`, `plan`, `apply` | stored PR target; config overlays; show/apply the materialization plan |
+
+## Overlay substrate
+
+gr2 also carries the config-overlay substrate (capture, compose, and materialize configuration layers over a workspace): see [docs/OVERLAY-SUBSTRATE.md](docs/OVERLAY-SUBSTRATE.md).
+
+## Development
+
+```bash
+pip install -e "gr2[dev]"    # from the repository root
+cd gr2 && pytest             # the gr2 suite (tests + overlay tests)
+cd gr2 && ruff check .       # lint, same config as CI
+```

{gitgrip-1.5.1 → gitgrip-2.0.0a2}/gitgrip.egg-info/SOURCES.txt

@@ -1,11 +1,5 @@
-MANIFEST.in
 README.md
-VERSION
 pyproject.toml
-_build/backend.py
-_build/version_from_cargo.py
-_build/__pycache__/backend.cpython-311.pyc
-_build/__pycache__/version_from_cargo.cpython-311.pyc
 gitgrip.egg-info/PKG-INFO
 gitgrip.egg-info/SOURCES.txt
 gitgrip.egg-info/dependency_links.txt
@@ -66,6 +60,7 @@ python_cli/events.py
 python_cli/execops.py
 python_cli/failures.py
 python_cli/file_exec.py
+python_cli/git_review.py
 python_cli/gitops.py
 python_cli/grip.py
 python_cli/grip_cli.py
@@ -80,8 +75,11 @@ python_cli/project_review.py
 python_cli/prune.py
 python_cli/push.py
 python_cli/review.py
+python_cli/review_dispatch.py
 python_cli/review_ephemeral.py
+python_cli/review_rebind.py
 python_cli/review_run.py
+python_cli/review_runners.py
 python_cli/spec_apply.py
 python_cli/staging_cleanup.py
 python_cli/syncops.py
@@ -97,6 +95,7 @@ tests/test_clone_materialization.py
 tests/test_commit.py
 tests/test_config_base_path_guard.py
 tests/test_config_overlay.py
+tests/test_conftest_git_isolation.py
 tests/test_contribution_protocol.py
 tests/test_ensure_lane_checkout_reference_clone.py
 tests/test_env_materialization.py
@@ -104,8 +103,12 @@ tests/test_event_log_integrity.py
 tests/test_event_outcome_policy.py
 tests/test_events.py
 tests/test_events_torn_line.py
+tests/test_exec_apostrophe_and_oserror.py
+tests/test_exec_single_string_and_materialize_plan.py
 tests/test_execops.py
 tests/test_failure_event_outcome.py
+tests/test_foreground_launch_runtime.py
+tests/test_git_review.py
 tests/test_gr2_packaging.py
 tests/test_gr2_review_receipt.py
 tests/test_grip_cli.py
@@ -118,6 +121,7 @@ tests/test_jsonl_store.py
 tests/test_lane_create_fork_base_cli.py
 tests/test_lane_lease_show_json.py
 tests/test_lane_lifecycle_safety.py
+tests/test_lane_repo_paths_and_all_skipped.py
 tests/test_lane_toml_serialization.py
 tests/test_launch_primitive.py
 tests/test_m2_overlay_hindsight.py
@@ -158,11 +162,13 @@ tests/test_pr_merge_partial_failure.py
 tests/test_project_file_materialization.py
 tests/test_project_review_range_reconstruction.py
 tests/test_project_review_three_repo.py
+tests/test_projection_tracked_dest.py
 tests/test_propagation_contribution.py
 tests/test_propagation_daemon.py
 tests/test_propagation_state_machine.py
 tests/test_prune.py
 tests/test_push.py
+tests/test_readme_verbs_exist.py
 tests/test_repo_status_linked_worktree.py
 tests/test_repo_status_schema_version.py
 tests/test_repo_status_symlinked_git_dir.py
@@ -172,19 +178,28 @@ tests/test_review_bind_verify.py
 tests/test_review_cli.py
 tests/test_review_close_gr.py
 tests/test_review_create_project_cli.py
+tests/test_review_dispatch.py
 tests/test_review_ephemeral.py
 tests/test_review_open_lane.py
+tests/test_review_rebind.py
 tests/test_review_run.py
 tests/test_review_run_import_isolation.py
 tests/test_review_run_rerun_and_refusal_receipt.py
+tests/test_review_runners.py
 tests/test_review_verify_inside.py
 tests/test_rmtree_or_refuse.py
+tests/test_single_repo_cwd_refusal.py
 tests/test_snapshot_id_prefix_resolution.py
 tests/test_spec_apply_event_outcomes.py
 tests/test_sprint21_sync_platform.py
 tests/test_staging_cleanup.py
+tests/test_store_verb_rename.py
 tests/test_sync_event_outcomes.py
+tests/test_sync_fast_forward.py
 tests/test_sync_fetch.py
+tests/test_sync_seed_local.py
+tests/test_sync_ssh_rewrite.py
+tests/test_sync_status_probe.py
 tests/test_target.py
 tests/test_tmux_launch_runtime.py
 tests/test_unit_abort.py
@@ -193,9 +208,10 @@ tests/test_unit_apply_dry_run.py
 tests/test_unit_manifest_schema.py
 tests/test_unit_propose.py
 tests/test_unit_topological_apply.py
-tests/test_version_single_sourced.py
+tests/test_version_static.py
 tests/test_workspace_convert_clone.py
 tests/test_workspace_edit_lease_cap.py
 tests/test_workspace_identity_boundary.py
 tests/test_workspace_init_from_topology.py
+tests/test_workspace_init_local_repos.py
 tests/test_workspace_snapshot.py

{gitgrip-1.5.1 → gitgrip-2.0.0a2}/gitgrip.egg-info/entry_points.txt

@@ -1,2 +1,3 @@
 [console_scripts]
+git-review = gr2.python_cli.git_review:main
 gr2 = gr2.python_cli.app:main

gitgrip-2.0.0a2/gr2/overlay/__init__.py

@@ -0,0 +1,9 @@
+"""gr2 overlay substrate: config-overlay capture, composition, and materialization.
+
+M1 scope: Tier A only (config files), eager materialization, trust-gated.
+
+The distribution version is single-sourced from the package metadata (the static
+number in gr2/pyproject.toml); this module carries no ``__version__`` literal so a
+stale third number cannot drift here. Read it with
+``importlib.metadata.version("gitgrip")`` or ``gr2 --version``.
+"""

{gitgrip-1.5.1 → gitgrip-2.0.0a2}/prototypes/concurrent_lease_stress.py

@@ -8,6 +8,7 @@ import json
 import multiprocessing
 import os
 import subprocess
+import sys
 import tempfile
 from pathlib import Path
 
@@ -65,7 +66,7 @@ repos = ["app"]
 def create_lane(root: Path, workspace_root: Path) -> None:
     run(
         [
-            "python3",
+            sys.executable,
             str(lane_proto(root)),
             "create-lane",
             str(workspace_root),
@@ -88,7 +89,7 @@ def worker(workspace_root: str, actor: str, queue, disable_locking: bool) -> Non
         env["GR2_LEASE_TEST_DELAY"] = "0.02"
     proc = run(
         [
-            "python3",
+            sys.executable,
             str(lane_proto(root)),
             "acquire-lane-lease",
             workspace_root,
@@ -154,7 +155,7 @@ def release_all(root: Path, workspace_root: Path, disable_locking: bool) -> None
     for actor in ("worker:a", "worker:b"):
         run(
             [
-                "python3",
+                sys.executable,
                 str(lane_proto(root)),
                 "release-lane-lease",
                 str(workspace_root),

{gitgrip-1.5.1 → gitgrip-2.0.0a2}/prototypes/concurrent_workspace_cap_stress.py

@@ -8,6 +8,7 @@ import json
 import multiprocessing
 import os
 import subprocess
+import sys
 import tempfile
 from pathlib import Path
 
@@ -65,7 +66,7 @@ repos = ["app"]
     for unit, lane in (("atlas", "lane-a"), ("apollo", "lane-b")):
         result = _run(
             [
-                "python3",
+                sys.executable,
                 str(lane_proto(root)),
                 "create-lane",
                 str(workspace_root),
@@ -100,7 +101,7 @@ def _acquire_worker(
         env["GR2_LEASE_TEST_DELAY"] = "0.04"
     result = _run(
         [
-            "python3",
+            sys.executable,
             str(lane_proto(repo_root())),
             "acquire-lane-lease",
             workspace_root,
@@ -190,7 +191,7 @@ def sequential_control() -> dict[str, object]:
             outcomes.append(
                 _run(
                     [
-                        "python3",
+                        sys.executable,
                         str(lane_proto(repo_root())),
                         "acquire-lane-lease",
                         str(workspace_root),