articles/2024/python-poetry-vs-uv/

[giscus[bot]]

articles/2024/python-poetry-vs-uv/

Comparing two Python package managers: Poetry and new kid on the block uv.

https://www.loopwerk.io/articles/2024/python-poetry-vs-uv/

[dusktreader]

I appreciate the article, and I share your sentiment. I don't feel that uv is quite ready to replace poetry in my workflows yet.

However, something caught my attention when you were suggesting that you can replace pyenv with uv. I've managed to do this, and there's a step that's very useful for getting poetry to use a python version installed via uv. I do not set a local version of python to create the .python-version file.

Instead, I initialize the virtual environment that poetry uses with a python version installed by uv. You can do that with one command using:

poetry env use $(uv python find 3.12)

You can, of course change the python version to whichever you prefer as long as it's installed on your system and uv can detect it.

After that, it's simply a matter of running poetry install to install your project. I've found this workflow is preferable to creating the .python-version file and committing it to source control.

Cheers!

[kfchou]

Can you think of any reasons to not do this the other way around? i.e., first create a venv with some python version with

uv venv .venv-3.12 --python 3.12

then activate it as usual. Since Poetry will use any existing venv for installation, do poetry install to install your requirements in that environment.

[dusktreader]

When I'm working with poetry, I don't like to work inside of activated virtual environments. Just a personal preference there.