RTrtpg·Jul 29, 2026
sorry, you're right and I didn't express my idea well
> For python - https://github.com/aspect-build/rules_py parses a UV lockfile and does not use either UV or pip at build time.
rules_python does for example call into piptools to do installation
https://github.com/bazel-contrib/rules_python/blob/main/pyth...
To be honest this stuff feels like it's gotten soooo much better in the years since I've used Bazel. (one can easily argue that it's been thanks to language ecosystems getting their things better) compared to when I've last had to use Bazel back in 2021-2022 (I had initially set up Bazel in ... 2018 for an existing Python project). So this might be a bit like relitigating Python 3.0. The lessons are learned perhaps!
If I want to be very cynical... I think there is a universe where uv could have existed 5 years earlier if Google had
Read the rest
decided "we're going to extract our Bazel learnings to get Python packaging to be better".
You might say "well they have blaze they don't need this" and that's kind of the point. In the world of setup.py you still need some language-specific infrastructure. Google and friends could have pushed things along in interesting ways, IMO!
But given their general sort of "we just vendor everything in" attitude they don't need to do that. So language ecosystems don't get the right kind of pushes and it takes us a decade for someone in the Python community to write "lockfiles that work + a package installer that works". Feels like a missed opportunity, mainly.