Skip to content

Makefile targets fail when only uv-managed Python is available #1740

Description

@kevinsslin

Summary

Several Makefile targets invoke bare python even though codex-lb documents uv as its project and Python environment manager. On systems that provide python3 and uv but no python alias, these targets fail before their scripts run.

Reproduction

$ command -v python
# no output
$ command -v python3
/opt/homebrew/bin/python3
$ command -v uv
~/.local/bin/uv
$ make architecture-check
python scripts/check_proxy_architecture.py
make: python: No such file or directory
make: *** [architecture-check] Error 1

Affected Makefile paths

  • architecture-check
  • integration-core shard verification
  • integration-core shard selection
  • wheel asset verification in package

Expected behavior

Makefile-owned Python tooling should run through the locked uv-managed project environment, consistent with the documented development workflow and existing uv run python / uv run ruff recipes.

Proposed fix

Replace the four host-level bare python invocations in Makefile with uv run python. Keep CI runner commands, container entrypoints, and Helm runtime scripts out of scope because those environments explicitly provision their Python executable.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions