Fabian Meumertzheim

Couldn't we just expose the `.bzl` files as `filegroup`s? That's what a number of other low-level modules (bazel_features, buildozer) have done.

I looked into this and the root cause is that: * *without* the flag, `ProtoInfo.proto_source_root` is `"external/maybe_rules_go_proto_bug~"` and the path of the proto is `"external/maybe_rules_go_proto_bug~/proto/foo.proto"` * *with* the flag, `ProtoInfo.proto_source_root`...

The `.processed` file is just a synthetic output file that's always empty: Bazel can't run actions that produce no outputs, so the way we get it to run on headers...

https://registry.bazel.build/modules/ape has cross-platform binaries for common utilities, including `unzip`.

@rickeylev Happy to help, but I would need to know whether there have been any intentional changes to the way Python imports are resolved.

When I run the reproducer, the `sys.path` looks like this: ``` ['/home/fhenneke/tmp/rules_python_1631_repro', '/home/fhenneke/.cache/bazel/_bazel_fhenneke/8c09f903aff88728a492063a5dce0a79/execroot/_main/bazel-out/k8-fastbuild/bin/hello_world.runfiles', ...] ``` This is why the `import` in `hello_world.py` resolves as it does: into the source root,...

I was using Python 3.10. That makes sense. @rickeylev I can look into handling this case in the runfiles library for compatibility with Python 3.10 and lower if those versions...

Thanks for working on this! Feel free to submit a patched module just like `circl`, I can review it. That said, I am planning to adapt the `clinkopts` logic in...

cc @sluongng

Thanks, I addressed your comments and am debugging the remaining test failure on Windows.