I personally prefer the rules_go way - where golang downloaded by bazel as external dependency and works without dependency to system golang.

Right now I have number of issues from my team related to small differences between "python" in PATH on OSX machines and small differences between python2.7 versions.

I want to see bazel as ultimate tool which allows to control which python should be used and bring it.

How it looks like with rules_go

git_repository(
  name = "io_bazel_rules_go",
  remote = "https://github.com/bazelbuild/rules_go.git",
  commit = "a960d7e60fa0e3c19f4b5970dd9ab283fb46d367",
)
load("@io_bazel_rules_go//go:def.bzl", "go_rules_dependencies", "go_register_toolchains")
go_rules_dependencies()
go_register_toolchains(go_version="1.9.2")

Uh oh!

Don't depend on the system python #42

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions