Paul Cody

Closing in favor of #389

Thank you for working on this! As a regular user, this was a significant pain point.

Closing due to age. If you still need help with this, will re-open.

With `--action_env=RULES_PYTHON_BOOTSTRAP_VERBOSE=1`: ``` Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging + STAGE2_BOOTSTRAP=unity/../rules_pycross/pycross/private/tools/_wheel_builder_stage2_bootstrap.py + PYTHON_BINARY=rules_pycross/pycross/private/tools/_wheel_builder.venv/bin/python3 + PYTHON_BINARY_ACTUAL= + IS_ZIPFILE=0 + [[...

Workaround with the following patch: ```diff commit 0ea27d6c87b21cd50878b6785f119786a11ca93b Author: Paul Johnston Date: Wed Oct 1 15:14:14 2025 -0600 wheel_builder: augment PYTHON_PATH for crossenv diff --git a/pycross/private/tools/wheel_builder.py b/pycross/private/tools/wheel_builder.py index d9ce8e0..7605083 100644...

Looks like it's the `PATH`. Any changes to `PATH` will trigger recompilation. Perhaps this is working as intended, or perhaps we can split it and use a set to dedup...

```sh $ uname -a Linux bina 4.13.0-46-generic #51-Ubuntu SMP Tue Jun 12 12:36:29 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux ```

Yes! Tested on bazel 0.21.0 and indeed no longer recompiles with `PATH` change. I guess I will go ahead and close this. The migration path from 0.19.2 to 0.20.0 and...

@hlopko I had observed it on linux & darwin before bazel 0.21.0. Now that I'm on 0.21 I'm really not seeing this anymore. For most projects I'm not using a...

Presumably this would all go away if the proto rules were starlarkified as has been discussed for several years. Any update from the bazel team on this?