Closed
Description
🚀 feature request
Creating this issue to encompass all of the PRs related to this feature, as the single research PR (#961) got a little bit too big for easy review.
Relevant Rules
gazelle Python plugin.
Description
Currently the gazelle plugin does not work if using bzlmod with bazel >= 6.0.0. This is due to:
- Gazelle and go toolchain is not present in
MODULE.bazelofrules_python, which means that the plugin reference fails. - The
all_whl_requirementshave labels, that do not work inbzlmoddue to repository remapping. Hence, themodules_mappingrule fails unless we do something about it. - Gazelle will generate dependency labels in the targets that do not work in
bzlmoddue to repository remapping.
Describe the solution you'd like
As researched in #961, we can fix these three issues separately:
- Adding gazelle and go as bzlmod deps.
- Changing the contents of the
all_whl_requirementsandall_requirementsbased on wetherbzlmodis used. - Have extra declaratives for changing the generated labels to work with bzlmod.
- Have extra aliases in the
@piprepo that work with both,bzlmodand classic gazelle. This might be similar to feat: add alias generation for pip parse #814, however this is not a requirement to make gazelle withbzlmodwork.
Describe alternatives you've considered
Rejected alternatives:
- Having a flag in
gazelle_python.yamlmanifest, which would say that we are usingbzlmod. The manifest should be the same irrespective of whether we are usingbzlmodor not due to the same reason why we may want to have aliases in@piprepo -- because we want to enable a smooth transition tobzlmodas described in the migration guide
Metadata
Metadata
Assignees
Labels
No labels