Unfortunately, for a lot of people (including myself), the choice is increasingly to just avoid Python whenever possible rather than try to delve into all of this. I didn't even know that _any_ of the tools were VC-backed.
It's how language ecosystems work when there's no authority with real power at the top. Python doesn't have real power at the top. Of late the SC thinks it wants to be that power. The developer base, mostly made up of people accustomed to both a language and community that is historically allergic to the idea that you can be told what not to do, largely disagrees. So, you get a cambrian explosion.
C# doesn't have this problem, for example -- though it has others. My (very brief) contact with rust crates as a user suggests that rust does; elisp/emacs absolutely does, and in spades; js might but i've never written a line so i don't know.
end of the day, python solves my business needs, so I've learned to walk the tangle. So much so that it makes sense, usually...
with no choice comes responsibility too, it's just that neither are yours, and likely aren't what you'd want.
edit: at this time, incidentally, i'm choosing to not use the VC-backed out-of-ecosystem toolchain (ruff, uv); pipx and setuptools do just fine.