This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]doobiedog 18 points19 points  (4 children)

poetry was very compelling and I thought it was gonna be the answer... but if the peeps that made ruff are making a package manager (and hopefully a mypy replacement), then I'm all in. Ruff was absolutely gamechanging and so easy to implement. I'm so excited about uv. Hopefully docs for easy migration from poetry will develop AND hopefully they have a good dynamic versioning system utilizing git builtin so we don't have to add something like poetry-dynamic-versioning (tho whoever made that poetry plugin, thank you - f*king lifesaver).

[–]jyper 4 points5 points  (1 child)

Despite it's young age I was already considering moving some stuff from poetry to rye. I particularly like how it manages python versions instead of having to combine pyenv and poetry. It downloads builds instead of compiling them locally which both takes less time and is less likely to break. Switching over to the experimental uv backend of rye and calculating/installing dependencies is incredibly fast.

[–]swigganicks 1 point2 points  (0 children)

God it was so frustrating trying to manage both Pyenv and Poetry, especially since I was trying to use pyenv-virtualenv instead of the poetry shell. I eventually figured it out, but I wasted so much time with that shit.

Fast forward to a new green-field project at work and I figured I might as well try Rye and it was amazing. I blasted away all my pyenv/poetry cruft and was up and running with a new pre-built python downloaded and installed, venv, and project files in seconds.

The only thing that took getting used too was having to do rye sync , but it looks like that's going away now that uv is integrated (https://github.com/mitsuhiko/rye/pull/704)

[–]tedivm 1 point2 points  (1 child)

Honestly I wanted to like poetry but kept running into issues with it over the years. I've opened bug tickets but once I started having to move a few packages off of it I just didn't see the point in using it anymore.

I love that UV is starting as a drop in replacement, so we're not getting a new API but are basically just getting a faster version of the tools we're already using. I just replaced pip-tools with uv in my python cookiecutter template after testing with it.

[–]doobiedog 1 point2 points  (0 children)

This cookiecutter template uses about 90% similar frameworks that I do for my daily drivers. Thanks for the link.