If you have uv installed, trying out Python 3.14 is as simple as running this command:
$ uvx python@3.14
Python 3.14.0 (main, Oct 7 2025, 15:35:21) [Clang 20.1.4 ] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>>
That was beautifully easy! (Make sure you're on the latest version of uv first (v0.9.0))
lunias 3 days ago [-]
uv: `An extremely fast Python package and project manager, written in Rust.`
Anyone else laughing out loud?
naldb 3 days ago [-]
Honestly, it’s pathetic. I know someone will come up with pragmatic reasons for this, but it’s simply pathetic.
zbentley 3 days ago [-]
It works well. I didn’t know what language it was written in, nor did I care, until months after starting to use uv. I still don’t care.
Sure, it’s a bit silly (I don’t think I’d go as far as “pathetic”, just silly) that the implementation language is above the fold in the description/readme. That’s a cosmetic gripe; it’s still a good tool.
Rust or not, writing a tool to manage installation of a language platform in something other than the language it manages is a good idea, it avoids bootstrap problems. Using something statically-ish linked is also good; it avoids problems caused by the bootstrap dependencies. Tools like pyenv have taught us that shell is a poor choice of bootstrap language. Rust seems as good a choice as any given that.
lunias 21 hours ago [-]
The humorous thing to me is how keenly aware of performance issues w/ Python the community is, but they continue to trudge along with it and develop tooling to support their Python efforts in other languages (C, Rust, Java, etc.) instead of just writing the entire program in another language.
Rendered at 10:10:14 GMT+0000 (Coordinated Universal Time) with Vercel.
(13 points, 18 hours ago, 3 comments) https://news.ycombinator.com/item?id=45502533
(37 points, 16 hours ago, 6 comments) https://news.ycombinator.com/item?id=45503617
(20 points, 12 hours ago, 10 comments) https://news.ycombinator.com/item?id=45507449
Anyone else laughing out loud?
Sure, it’s a bit silly (I don’t think I’d go as far as “pathetic”, just silly) that the implementation language is above the fold in the description/readme. That’s a cosmetic gripe; it’s still a good tool.
Rust or not, writing a tool to manage installation of a language platform in something other than the language it manages is a good idea, it avoids bootstrap problems. Using something statically-ish linked is also good; it avoids problems caused by the bootstrap dependencies. Tools like pyenv have taught us that shell is a poor choice of bootstrap language. Rust seems as good a choice as any given that.