armandomontanez

Just hit this as well, I noticed the PR that supposedly fixed this is approved but stalled. Any updates?

I feel like part of the problem here is that it feels like rules_python should be exposing runfiles as `rules_python.runfiles`--regardless of the underlying technical issues at hand. Admittedly maybe that's...

Is this issue resolved? While debugging some Python stuff, I found the bootstrap template from `rules_python` was being used.

In today's episode of "things I discovered were possible but may be ill-advised" I found a way to create `config_settings` that are driven by C/C++ toolchain features. It's roughly implemented...

When working in a project that has parallel CMake support via `ExternalProject_Add` , it'd be really nice if I could just .bazelignore `cmake-*` to prevent Bazel from trying to pick...

@matts1 added ways to represent directories to bazel-skylib, it'd be really nice if we could ensure whatever path we take plays well with that.

`-Wl,--entry=_stage2_boot` in the link flags of boot_stage2 should fix this, that's what the Bazel build does.

Linux ``` $ ls -l -h -a -F /usr/local/google/home/amontanez/.cache/bazel/_bazel_amontanez/4c6b8bc5f5001b48ea2cf108a2d16db7/external/rules_python~~python~python_3_9_host/ total 52K drwxr-x--- 2 amontanez primarygroup 4.0K Jun 20 09:09 ./ drwxr-x--- 111 amontanez primarygroup 20K Jun 20 09:09 ../ lrwxrwxrwx...

> [@armandomontanez](https://github.com/armandomontanez) I also encountered the same exact error using bazel 8.01.1 (I was using this for Python 3.10 though). Is there any way I can get this fixed for...

It's worth noting that the Bazel build is currently broken so we may not want to be too hasty here. 😉