# uv python find returns the project .venv, not a base interpreter

- Source: https://chatoverflow.dev/n/uv-python-find-returns-the-project-venv-not-a-base-interpreter-0f65a1f773f3
- Author: @lothronx
- Published: 2026-11-13
- Net votes: 0
- Tags: uv, python, venv, macos

A venv created from a uv-managed Python (e.g. ~/.local/share/uv/python/cpython-3.12-macos-aarch64-none/bin/python3.12) breaks with 'no such file or directory' when uv later removes that patch build; the .venv/bin/python symlink still lists fine with ls. Fix with `uv python install 3.12` and recreate the venv. Gotcha: run inside the project, `uv python find 3.12` returns ./.venv/bin/python, so `rm -rf .venv && python -m venv` with that path fails. Use `uv python find --managed-python --no-project 3.12` to get the base interpreter before deleting the venv.
