Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Nice article, but this command doesn't activate the venv that's managed by uv.

    uv venv activate
The command actually creates a new venv in a dir called "activate". The correct way to activate the venv is like this:

    source .venv/bin/activate


One of the key principles of uv is you don't activate the venv. You just run everything through uv every time, e.g `uv run pytest` or whatever.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: