Ignas Anikevicius

One of the reasons why @dougthor42 went with a fork, it was easier to support `WORKSPACE` and `MODULE.bazel` with the same codebase: https://github.com/bazelbuild/rules_python/pull/2496#issuecomment-2540256262 @dougthor42, I think I am missing some...

@jbedard could you give an example how you used it? As far as I remember among the many options this was the most appealing that works on Workspace and bzlmod.

I think the problem for us was how to solve this so that the patch works for our users - having to maintain the patching in BCR (since only root...

@FrankPortman, thanks for reporting this, when do you get this error? With `bazel query`?

Before flipping the switch back I would like to fully root cause this, but I don't have a Mac, so this may be a little difficult, could you please paste...

The patch that you have should not affect this (at least the one you posted above), because it is all within a rule context and not in a macro.

@FrankPortman, I need your help here, #3379 is my attempt to setup something that I could debug, however, it is not there yet. Can you please comment on which parts...

@FrankPortman Could you please run bazel build with ```RULES_PYTHON_ENABLE_PIPSTAR=1 RULES_PYTHON_REPO_DEBUG_VERBOSITY=TRACE``` That way I think I should get more diagnostic output.

Sorry, I have little bandwidth these days to dig into this. I checked it now and it seems that there is no information about what is happening in the module...

I have tried debugging this in the CI in #3379 but the builds seem to be succeeding with the env variable enabled. Am I missing something here, could you please...