dev dependency on uv is not great

[jku]

I like uv but ... This is the developer experience of this project on a typical OS:

$ make dev
uv venv
make: uv: No such file or directory
make: *** [Makefile:12: env/pyvenv.cfg] Error 127
$ 

What now?

• do I manually create a virtual env just so I can install the packages required to create the virtual env the makefile wants?
• Could there be an alternative here that Just Works as long as Python is installed?

[woodruffw]

Yeah, I agree that's not ideal. IMO it's okay to have a development tool dependency on uv here, but we should probably document it explicitly somewhere in the README or a new CONTRIBUTING file?

[jku]

• I think uv venv does nothing special so maybe there could just be a step that runs python3 -m venv .venv && . ./.venv/bin/activate && pip install uv if uv is not available
• the Makefile seems buggy as well: targets use paths in env/ but uv env actually creates .venv/