Switching from Pyenv to Uv
bluesock.org
Switching from Pyenv to Uv
1–10 of 239 posts
Re: Switching from Pyenv to Uv
#2has anybody doing complex projects achiever success with uv completely replacing pyenv, and had mostly pros and few or no cons?
I'm very comfortable with pyenv, but am extremely open to new stuff
Re: Switching from Pyenv to Uv
#3has anybody doing complex projects achiever success with uv completely replacing pyenv, and had mostly pros and few or no cons? I'm very comfortable with pyenv, but am extremely open to new stuff
I've used uv to work on the feast feature store project to great success
Re: Switching from Pyenv to Uv
#4Is there a guide for how to use uv if you're a JS dev coming from pnpm?
I just want to create a monorepo with python that's purely for making libraries (no server / apps).
And is it normal to have a venv for each library package you're building in a uv monorepo?
Re: Switching from Pyenv to Uv
#5Is there a guide for how to use uv if you're a JS dev coming from pnpm? I just want to create a monorepo with python that's purely for making libraries (no server / apps). And is it normal to have a venv for each library package you're building in a uv monorepo?
If the libraries are meant to be used together, you can get away with one venv. If they should be decoupled, then one venv per lib is better.
There is not much to know:
- uv python install if you want a particular version of python to be installed
- uv init --vcs none [--python ] in each directory to initialize the python project
- uv add [--dev] to add libraries to your venv
- uv run when you want to run a command in the venv
That's it, really. Any bonus can be learned later.
Re: Switching from Pyenv to Uv
#6Uv in script mode has made me love python again.
Re: Switching from Pyenv to Uv
#7has anybody doing complex projects achiever success with uv completely replacing pyenv, and had mostly pros and few or no cons? I'm very comfortable with pyenv, but am extremely open to new stuff
Sure, I've basically replaced pyenv, pyenv-virtualenv, poetry; with uv.
I can't think about cons personally, though you might need to dig into the docs at times.
Re: Switching from Pyenv to Uv
#8Is there a guide for how to use uv if you're a JS dev coming from pnpm? I just want to create a monorepo with python that's purely for making libraries (no server / apps). And is it normal to have a venv for each library package you're building in a uv monorepo?
If the libraries are meant to be used together, you can get away with one venv. If they should be decoupled, then one venv per lib is better. There is not much to know: - uv python install if you want a particular version of python to be installed - uv init --vcs none [--python ] in each directory to initialize the python project - uv add [--dev] to add libraries to your venv - uv run when you want to run a command i…
There's also workspaces (https://docs.astral.sh/uv/concepts/projects/workspaces/) if you have common deps and it's possible to act on a specific member of the workspace as well.
Re: Switching from Pyenv to Uv
#9has anybody doing complex projects achiever success with uv completely replacing pyenv, and had mostly pros and few or no cons? I'm very comfortable with pyenv, but am extremely open to new stuff
I worked in a large-ish org where 20+ python projects, their CI/CD pipelines and their docker images were migrated from `pyenv` + `.python-version` + `requirements.txt` to `uv` in basically a single day.
If you are comfortable with `pyenv`, the switch to `uv` is basically a walk in the park. The benefit is the speed + the predictable dependencies resolution.
Re: Switching from Pyenv to Uv
#10I decided to give uv a shot on my new machine over pyenv and I've been enjoying it. Just last week I had to generate out 90 slides from some data last minute. Quickly created a project added in my dependencies (pandas, matplotlib, python-pptx), then crunched out some code. Absolutely zero friction with a much easier to use set of commands in my opinion.