This is a lovely conversation, with some interesting thoughts on the recent progress of uv.

For all the concerns raised, I’d be happy if I could see a plan to merge the available performance wins (non just “it’s Rust” ones) back upstream into pip.

Bring on the money, but plan for when it goes away, is more or less my take. We still need native community owned tooling on that day.

From: @jacob
https://social.jacobian.org/@jacob@jacobian.org@jacob@jacobian.orgian.org/113091418140504394

@carlton @jacob Yes to bringing back some lessons learned to pip, but

if Astral implodes tomorrow, doesn't uv continue working? Couldn't the community just fork it and continue its development, arguably at a slower pace?

Colour me sceptical that the community at a whole is far enough onto the Rust bandwagon that it would continue to be maintained as a fork.

I'd like to see the Python native tooling advanced, and then there's a case for (maybe) sprinkles of Rust.

There's a separate 'single binary' argument that I'm not unsympathetic to, but self bootstrapping pure Python installations have themselves (too) come on.

I would be more worried about CPython dependence on corporate sponsorship than uv at this point to be honest. Who's funding the free-threaded version? The advancements in typing?

@astrojuanlu @carlton Those aren't single-stakeholder things though? Like, there's an entire foundation and as well as checks & balances around the actual work to ensure that things are aligned with the broader needs on them.