Ignas Anikevicius
Ignas Anikevicius
I think that something related to this got fixed in `bzlmod` by us starting to use `is_python_x.y` instead of `is_python_x.y.z` config_settings in the hub repos. That might be still present...
Right now the behaviour is that you get the latest. With `bzlmod`, you should be able to specify it in the `.bazelrc` and get what you would expect, I think.
I agree that we should probably just register the latest versions by default.
Another method to override the URLs to the internal rules_python dependencies would be through the use of the bazel downloader, see https://blog.aspect.dev/configuring-bazels-downloader This way is much more robust and sustainable...
#1827 got merged and I think it should work now. Please test and let me know what breaks, this will help enable the feature by default.
The downloader setup is present, so everything should be working, please let me know if that is not the case.
Please add more details to the issue as it is hard to understand what exactly is breaking. Could you add a reproducible example please?
Reopening as the feature for including build deps in pip-tools got merged so the definition of done here could be to ensure that it is available in rules_python.
I am not sure if changing this won't have any unintended consequences. I've linked a few tickets here: 1. People may depend on `site-packages` being present in the path. See...
Thanks for the context, I'm fine with this behaviour being gated under a feature flag.