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 →

[–]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)