Alex Eagle
Alex Eagle
Oh I see now. I wonder if it's related to "pystar" https://github.com/bazelbuild/rules_python/issues/1069
A contribution here would be great. Note that we've recently switched to use `uv` for creating the virtualenv, so likely whatever support is needed to make console scripts functional is...
If you switch to pulling rules_py from a SHA rather than a release, you'll get the "pre-release" which exposes the rust sources to your build and you can test this...
+1 there are some fixes on `main` that we need in the Bazel ecosystem.
I think this is https://github.com/Tinder/bazel-diff/issues/134 where it was described as "expected behavior"
It's really hard to get enough focus time from any of the folks you @-mentioned here to review something that's larger than bite-sized. I don't want to lose your improvements...
@albertocavalcante I haven't heard from @peakschris in a while. Perhaps you could pick this up and submit some targeted PRs for the bits that can land without much controversy?
I believe we fixed this by using the hermetic `tar` from bazel-lib
I have not seen a migration plan for that. I don't think it's a wise plan to remove these from rules_python at this point. In fact much of the ecosystem...
I find it confusing as well. The recent changes are anonymous and have no context or indication of what they are doing: