forked from hdl/bazel_rules_hdl
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Fixes to allow downstream project to set a different Python toolchain.
Previously, in the typical use case where `python_interpreter_target` is passed, the @bazel_rules_hdl//:init.bzl init macro would always call the vendored `install_deps`. However, this would only work if the passed in toolchain name matched the one used to generate the vendored requirements.bzl (since @python39 is hardcoded as a default inside). Now, we pass along any interpreter args to the vendored `install_deps` to override the defaults as documented at: https://github.com/bazelbuild/rules_python/blob/main/examples/pip_parse_vendored/README.md. This also eliminates the documented requirement to use the generated pip deps instead of the vendored version if an interpreter arg is set. We also update rules_python to the latest version, allowing the use of the "_host" toolchain label to avoid loading the interpreter per bazelbuild/rules_python#1644. Finally, we clean up other references to the pip_parse repo (which was only intended for the vendoring) and move them to use the vendored deps directly.
- Loading branch information
Showing
9 changed files
with
111 additions
and
59 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
This file contains 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
Large diffs are not rendered by default.
Oops, something went wrong.
This file contains 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
This file contains 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
This file contains 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
This file contains 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