Ignas Anikevicius

Just a quick note, but I think the recently added exec toolchain should help here. This was added for precompiling stuff, but it should be also applicable here.

Adding a tag to show that this is up for grabs if anybody in the community wants to contribute.

I agree that the `py_cc_toolchain` should have the unstable ABI ext suffix, but I am not sure that the toolchain should select whether `abi3.so` or the unstable ABI is used....

A PR to drop packages that are not common to all versions would be welcome. EDIT: just a few pointers what would need to change. 1. Currently [this line](https://github.com/bazel-contrib/rules_python/blob/main/python/private/pypi/extension.bzl#L515) just...

For completeness, if we want to distribute binaries together with rules_python releases, I think Aspect has a blogpost on something related: https://blog.aspect.build/releasing-bazel-rulesets-rust They are using rust to create their launcher...

Continuing from https://github.com/bazel-contrib/rules_python/issues/2156#issuecomment-2907717437 FYI in https://github.com/bazel-contrib/rules_python/blob/main/python/private/stage1_bootstrap_template.sh#L9-L37 we have the following things that the shell script needs to be templated for: * stage2_bootstrap location - this is the Python part of...

I see how this could be done with a three stage bootstrap, but with 2 stage bootstrap it might be tough due to the number of things that we expose....

Just what I wrote in #2529: Just to write here what I wrote in a related thread on Slack. I think what is happening here is: * The default python...

Just to write it down some thoughts: If we want to set `target_compatible_with` (and sometimes it makes things more annoying to work with), then we can do it in 2...

I think this may be duplicate of #1913. Does the error go away when using https://github.com/bazel-contrib/musl-toolchain or similar?