The uv build back end is now stable

(docs.astral.sh)

129 points NeutralForest | 1 comments | 03 Jul 25 11:51 UTC | HN request time: 0.315s | source

Show context

loks0n ◴[03 Jul 25 13:30 UTC] No.44454861[source]▶

Feels like Astral are going to eat the whole python eventually.

Makes me wonder, did the Python core team fail to see the opportunity in python tooling, have no desire to build it, or they didn't have the skills?

replies(4): >>44454925 #>>44454940 #>>44455089 #>>44455164 #

pjc50 ◴[03 Jul 25 13:36 UTC] No.44454925[source]▶

>>44454861 #

The python team build python. I suspect that insulates them from the actual problems of trying to build things with python. Also this sort of thing gets bogged down in approval processes. People have spent decades trying to "fix" python packaging; the important thing is that uv doesn't change any of that, it's a drop in replacement.

replies(1): >>44455827 #

1. troyvit ◴[03 Jul 25 15:06 UTC] No.44455827[source]▶

>>44454925 #

Yeah it reminds me of bun, for node, in that way (and that probably exposes how well I understand tooling). It's like somebody just swept everything off the table and started over.

I never learned python the way I wanted to because for years I would first look at the excruciating transition from v2 to v3 and just not see a point of entry for a newb like me.

Now the same thing is happening with tooling for v3. pip? pepenv? python pip? python3 pip? I don't freakin' know. Now there's uv, and I'm kinda excited to try again.

↑