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

To be honest, this was just a matter of time. As a long time Python developer, I just can’t wrap my head around the lack of something like this. GitHub was going to get hosted packages for Python but never did because it “didn’t align with their strategy objectives and a reallocation of resources” [1] (or some other similar corpospeak) Astral is a great company and I think we can’t question what they’ve achieved and provided to the Python community. uv is a game changer and solves one of the core issues with Python by providing a unified tool that’s also fast, reliable and easy to use. In fact, after using uv for the first time (coming from a combination of pyenv + poetry) I never wanted to go back and this is something all of my peers have experienced too. I’m glad it’s Astral who is doing this, and of course they will have to make money one way or another (which is perfectly fine and I don’t think anyone on this forum can be against that, as long as they are actually providing real value) but I was honestly tired of the paralysis on this matter. I did try to build a registry (pyhub.net) but being just one person with almost no resources and having another full time business made it impossible. Anyway, congrats to the team for the effort! [1] https://github.com/orgs/community/discussions/8542


Is this problem also solved by storing software artifacts in OCI container image registries that already support SLSA-compliant TUF signatures?


Anaconda solved the same problem ~10+ years ago already.


HAHAHAH don't even get me started on how bad anaconda is. On how slow the installer + interpreter, how they avoided being a part of the usual pip workflow, bloated environment, cross platform inconsistencies, extremely slow dependency resolution, etc etc etc...


Plus it took the name of an existing (fairly big) project


Posit has solved similar problems with their Package Manager as well, the benefit being that it's hosted on-prem, but the user has to build wheels for their desired architecture (if they're not on pypi).


to be honest. ill never use uv. python ecosystem tools should be in python.


This is very close minded. It's best to avoid statements like that.

I feel like having a working python environment is not a great requirement to managing your python environment.


My OS has hard dependency on python, so i'll always have working python environment.

Also, i tend to run pip like 4-5 times max (except initial package installations) during whole project lifetime, or not at all if packages are in distro already. Its speed is ok for that. So I'm not sure what "should" i miss.


is this ragebait ?

most of the stuff in the python ecosystem have a core built in C, including the language itself.


Definitely has never seen/used uv


Wait until you find out what language Python is written in.


Last time I looked it was in C.


Why?


+1


This is quite a disappointing self-limitation given the improvements uv brings to the table. You’re missing out on some good stuff.


I don't think so. It'd be best to fix native tools.


this is the kind of statement that will get anyone who works for me PIPd




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

Search: