You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat(bzlmod): removing incompatible aliases flag for bzlmod
With workspace, we need incompible aliases, because you get @pip//tabulate or @pip_tabulate//:pkg.
The requirement() macro hides this, but if you're manually referencing things, then changing the
flag ends up being a breaking change With bzlmod, though, the @pip_tabulate style isn't a
realistic option (you'd have to use_repo everything, a huge pain).
So we have choosen to always have `@pip//tabulate`.
Copy file name to clipboardExpand all lines: BZLMOD_SUPPORT.md
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -31,7 +31,7 @@ A second example, in [examples/bzlmod_build_file_generation](examples/bzlmod_bui
31
31
32
32
This rule set does not have full feature partity with the older `WORKSPACE` type configuration:
33
33
34
-
1.Multiple pip extensions are not yet supported, as demonstrated in [this](examples/multi_python_versions) example.
35
-
2.Gazelle does not support finding deps in sub-modules. For instance we can have a dep like ` "@our_other_module//other_module/pkg:lib",` in a `py_test` definition.
34
+
1.Gazelle does not support finding deps in sub-modules. For instance we can have a dep like ` "@our_other_module//other_module/pkg:lib",` in a `py_test` definition.
35
+
2.We have some features that are still not fully flushed out, and the user interface may change.
36
36
37
37
Check ["issues"](/bazelbuild/rules_python/issues) for an up to date list.
0 commit comments