build(make): prefer .venv tooling for Python targets

[armenzg]

Makefile Python targets now prefer tools from .venv/bin when a local virtualenv exists.

Previously, build-py, test-py, docs, update-venv, and package-py called bare python/pip/pytest, which could silently use an ambient interpreter. This updates those targets to resolve .venv/bin/* first and fall back to PATH only when .venv is not present.

That keeps local and CI-like workflows aligned with the project environment without breaking first-run setups.

Made with Cursor

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Bugbot Autofix prepared a fix for the issue found in the latest run.

• ✅ Fixed: Relative venv paths break after cd into subdirectories
  • Changed PYTHON, PIP, PYTEST, and SABLEDOCS variables to use absolute paths with $(CURDIR) prefix instead of relative .venv/bin/* paths.

Or push these changes by commenting:

@cursor push a4edc7b3b8

Preview (a4edc7b3b8)

diff --git a/Makefile b/Makefile
--- a/Makefile
+++ b/Makefile
@@ -3,10 +3,10 @@
 
 # unstable protos are only included in local development and not part of release packages
 SENTRY_PROTOS_BUILD_UNSTABLE := 1
-PYTHON ?= $(if $(wildcard .venv/bin/python),.venv/bin/python,python)
-PIP ?= $(if $(wildcard .venv/bin/pip),.venv/bin/pip,pip)
-PYTEST ?= $(if $(wildcard .venv/bin/pytest),.venv/bin/pytest,pytest)
-SABLEDOCS ?= $(if $(wildcard .venv/bin/sabledocs),.venv/bin/sabledocs,sabledocs)
+PYTHON ?= $(if $(wildcard .venv/bin/python),$(CURDIR)/.venv/bin/python,python)
+PIP ?= $(if $(wildcard .venv/bin/pip),$(CURDIR)/.venv/bin/pip,pip)
+PYTEST ?= $(if $(wildcard .venv/bin/pytest),$(CURDIR)/.venv/bin/pytest,pytest)
+SABLEDOCS ?= $(if $(wildcard .venv/bin/sabledocs),$(CURDIR)/.venv/bin/sabledocs,sabledocs)
 
 .PHONY: update-venv
 update-venv:

_{You can send follow-ups to the cloud agent here.}

^{Reviewed by Cursor Bugbot for commit 0710e7e. Configure here.}

[markstory]

Should we be switching over to uv run instead?

[armenzg]

Sounds good 👍🏻

[armenzg]

Good callout. I kept this PR on the existing devenv/pip flow to keep scope tight, but I pushed a follow-up commit that fixes the path issue by resolving .venv tools with absolute $(CURDIR) paths so subdirectory recipes work reliably.

If you want, I can open a separate PR to evaluate moving these Make targets to uv run end-to-end.