That's a good introduction, thank for this. Wondering though: why didn't you use that `uv init` creates the subdirectory? Are you aware that instead of activating the venv, you could also just use `uv run python -m main.py`. This allows you to almost forget about the venv.
Thanks Jan! I think I'm not aware of the `uv init` option you're suggesting, what would you have run instead? Thanks in advance for sharing.
About `uv run` I am indeed aware and I know a lot of people who use it, but I think it's more ergonomic to activate the venv once and then directly run the shorter commands. For one, typing `uv run` a lot adds up fast. Second, directly running commands gives you proper shell completion, which doesn't work (at least for me) with the `uv run` wrapper. But I admit that this is just a personal preference so if you're more comfortable with `uv run` and not activating the venv then there're no problem with that, keep using it!
That's a good introduction, thank for this. Wondering though: why didn't you use that `uv init` creates the subdirectory? Are you aware that instead of activating the venv, you could also just use `uv run python -m main.py`. This allows you to almost forget about the venv.
Thanks Jan! I think I'm not aware of the `uv init` option you're suggesting, what would you have run instead? Thanks in advance for sharing.
About `uv run` I am indeed aware and I know a lot of people who use it, but I think it's more ergonomic to activate the venv once and then directly run the shorter commands. For one, typing `uv run` a lot adds up fast. Second, directly running commands gives you proper shell completion, which doesn't work (at least for me) with the `uv run` wrapper. But I admit that this is just a personal preference so if you're more comfortable with `uv run` and not activating the venv then there're no problem with that, keep using it!
`uv init alice` creates the folder directly. Didn't think about shell completion, thanks for sharing this