-
-
Notifications
You must be signed in to change notification settings - Fork 632
fix(bzlmod)!: Remove ability to specify toolchain repo name. #1258
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
0f39e4c
7ce22e6
266f86e
bd82b31
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -14,11 +14,10 @@ local_path_override( | |
|
||
python = use_extension("@rules_python//python/extensions:python.bzl", "python") | ||
python.toolchain( | ||
name = "python3_9", | ||
configure_coverage_tool = True, | ||
python_version = "3.9", | ||
) | ||
use_repo(python, "python3_9") | ||
use_repo(python, "python_3_9") | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. So if we register 3.9.11, what is the name? I assume it is 3_9_11. We need to document this pattern somewhere. Update the documentation in the tag class and also update the documentation in the MODULE.bazel files. How the names generated gave me heartburn when I had less bazel experience. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. We don't support registering patch versions, just major.minor. I added doc to the tag class. Which module file are you referring to? I'm guessing the bzlmod example? I've updated the comment there about the name. |
||
|
||
# We are using rules_proto to define rules_proto targets to be consumed by py_proto_library. | ||
bazel_dep(name = "rules_proto", version = "5.3.0-21.7") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@rickeylev any reason these are here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, they make
bazel test ...
(from the rules_python workspace) ignore the generated symlinks in the example sub-directory workspaces. Otherwise it'll recurse into them and find the various BUILD files and try to interpret them.