Post #2724563
2026-05-01 13:01 UTC
@tastapod@mas.to pretty much what you write is what I sort of expected.
* uv init in an existing project folder does almost nothing of value. Even if there are sources in the folder it keep creating main.py. Yupee!!!
* there's no venv being created
It seems there's a gap somewhere.
Replies (1)
-
@tastapod@mas.to 2026-05-01 15:48
@al3x@hachyderm.io if you already have a project.toml, say, then uv init is a no-op. It won't overwrite anything. Check https://docs.astral.sh/uv/guides/migration/pip-to-project/#migrating-to-a-uv-project and note that uv doesn't care about an 'active' venv as such, it just manages a local one in .venv in any project. I still tend to activate it anyway out of habit, so I can run `python` directly rather than `uv run`, but that's habit. https://docs.astral.sh/uv/guides/migration/pip-to-project/#project-environments Finally, migrate-to-uv should get you a lot of the way there: https://osprey-oss.github.io/migrate-to-uv/