Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> Please consider consolidating python dependency management instead of fragmenting it

You realize that this project predates uv by roughly a decade, right?



[flagged]


Can you expand on what you mean, exactly?


They thought they had a better advertising chance for `uv` than they actually did. As far as I can tell, `uv` is a replacement for `pip`. But the project linked by OP doesn't actually replace `pip`, but rather a small subset of functionality in `pip` - `pip freeze`. Unless `uv` has some sort of import scanning functionality, the suggestion to use `uv` instead doesn't really make any sense.


On the contrary, read this about `uv` by the author of `rye`:

https://lucumr.pocoo.org/2024/8/21/harvest-season/

Domination is a goal because it means that most investment will go into one stack. I can only re-iterate my wish and desire that Rye (and with it a lot of other tools in the space) should cease to exist once the dominating tool has been established. For me uv is poised to be that tool. It's not quite there today yet for all cases, but it will be in no time, and now is the moment to step up as a community and start to start to rally around it.

Yes, I linked to an obscure feature uv supports. It's already a rather lot more.


Again, you seem to be arguing against points no one is making. uv is rad, you don't have to convince me. But people are still going to use pip for awhile and if they do, the repo in OP is helpful. You need to apply your zealotry to relevant situations for it to be effective.

You are talking past people. It comes across like you're not reading comments with sincerity but rather as an empty vessel to attach your own personal opinion as a rebuttal.

For instance, the rye authors views (no one mentioned rye btw) have little bearing on how uv helps in this particular instance.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: