docs: using python_version attribute for specifying python version#2589
Merged
rickeylev merged 2 commits intobazel-contrib:mainfrom Jan 28, 2025
Merged
docs: using python_version attribute for specifying python version#2589rickeylev merged 2 commits intobazel-contrib:mainfrom
rickeylev merged 2 commits intobazel-contrib:mainfrom
Conversation
rickeylev
approved these changes
Jan 28, 2025
Collaborator
rickeylev
left a comment
There was a problem hiding this comment.
They didn't permit those trivial/mechanical changes to BUILD.bazel? Well, ok then.
We still appreciate your doc contributions!
Contributor
Author
|
Hi @rickeylev I left out |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Updates examples and docs to tell to use the base rules and the python_version attribute
instead of the wrapper transition rules.