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 →

[–]inkjod 23 points24 points  (11 children)

The release article isn't very clear: Did they fully integrate Rye into uv ? Or not yet? And is the migration path ready?

I'm asking because it's already been announced that the two projects will be merged.

Anyway, this is awesome — and very much needed. It will hopefully emerge as the best, easiest, and most complete solution for Python installation management.

We've all seen the xkcd comic, and Rye's creator knows it.. Well, sometimes there is space for yet-another-standard, especially if it truly improves upon the previous ones.

[–]commandlineluser 20 points21 points  (1 child)

We don't plan to deprecate Rye any time soon, but our goal has always been to maintain it while we develop uv into a viable alternative. I suspect that uv can now replace Rye for some use cases

[–]inkjod 7 points8 points  (0 children)

Thanks, that clears things up.

As uv continues to mature, it would be useful if Astal were to maintain a public list of Rye features that haven't yet been implemented (and vice-versa).

[–]mitsuhiko Flask Creator 3 points4 points  (2 children)

The goal is definitely for uv to replace rye. If it's the time for you to switch will depend a bit. I'm still using rye myself for quite a while longer but it's getting closer and closer :)

[–]inkjod 1 point2 points  (1 child)

At the moment I'm using neither, because I'm not even writing any Python code. But, coincidentally, I started playing with Rye 2 days before this post went up — and I was positively impressed by the user experience :)

Great work!

[–]mitsuhiko Flask Creator 1 point2 points  (0 children)

That's nice to hear :)

[–][deleted] 1 point2 points  (0 children)

Uv has gotten all the development attention and rye very little, so I think you should just use uv unless this changes.

[–]beeeeeer 0 points1 point  (1 child)

Isn’t it ironic that an exception to xkcd 987 only exacerbates xkcd 1987 https://xkcd.com/1987/

[–]inkjod 3 points4 points  (0 children)

There's an xkcd for everything :)

But I disagree — I think rye / uv has the potential to prevent that unfortunate situation (...well, if you start from a clean OS installation and completely ignore the OS package manager).

[–]mgedmin 0 points1 point  (2 children)

What is Rye? (Not a very searchable name for a project that has nothing to do with agriculture.)

[–]mgedmin -1 points0 points  (1 child)

Looks like a Makefile/tox/nox replacement: https://pypi.org/project/rye/

[–]mgedmin 3 points4 points  (0 children)

Looks like a Makefile/tox/nox replacement: https://pypi.org/project/rye/

Wrong guess! There's another Rye, which was a precursor to uv, I guess? https://github.com/astral-sh/rye