🐛 Allow uv to be managed outside of .local/cargo/bin

[larsyencken]

Fixes https://github.com/owid/ops/issues/229

• Lets the user decide where and how to install uv, and makes them responsible for putting it in their PATH
• Gives an error if uv is not installed, suggesting brew install uv as a resolution for the user

[owidbot]

Quick links (staging server):

Site	Admin	Wizard

Login: ssh owid@staging-site-uv-fix

chart-diff: ✅

No charts for review.

data-diff: ✅ No differences found

Legend: +New  ~Modified  -Removed  =Identical  Details
Hint: Run this locally with etl diff REMOTE data/ --include yourdataset --verbose --snippet

Automatically updated datasets matching weekly_wildfires|excess_mortality|covid|fluid|flunet|country_profile|garden/ihme_gbd/2019/gbd_risk are not included

Edited: 2024-10-01 11:21:55 UTC
Execution time: 18.50 seconds

[Marigold]

@larsyencken how about this? .cargo/env adds uv to the path which works for CI, and it doesn't do anything for users who installed it via brew.

(Alternatively, I can install uv explicitly in all Buildkite steps & CI)

install-uv-default:
	@if ! command -v uv >/dev/null 2>&1; then \
		echo '==> UV not found. Installing...'; \
		curl -LsSf https://astral.sh/uv/install.sh | sh; \
	fi

.venv-default: install-uv .sanity-check
	@echo '==> Installing packages'
	@if [ -n "$(PYTHON_VERSION)" ]; then \
		echo '==> Using Python version $(PYTHON_VERSION)'; \
		export UV_PYTHON=$(PYTHON_VERSION); \
	fi
	[ -f $$HOME/.cargo/env ] && . $$HOME/.cargo/env || true && uv sync --all-extras

[larsyencken]

@Marigold Overall it looks good, especially if there's nowhere else we need uv, i.e. if all other parts of the recipe just use .venv/bin/<blarg> to do their thing.