grpc/third_party/futures.BUILD

py_library(
  name = "futures",
  srcs = glob(["concurrent/**/*.py"]),
  srcs_version = "PY2AND3",
  visibility = ["//visibility:public"],
)
Separate py_grpc_library and py_proto_library. By popular demand, we'll now be offering separate py_grpc_library and py_proto_library targets sharing the same interface as within google3. This change necessitated some modifications to how we pull in our own Python-level dependencies and how we make those available to those pulling in our project via Bazel. There is now a grpc_python_deps() Bazel workspace rule that pulls in the appropriate dependencies, which should be called from the client project's WORKSPACE file. A test has been added to the bazel/test/ directory to verify that this behavior works as intended. It's worth noting that the protobuf repository's usage of Starlark bind() caused a great deal of trouble in ensuring that we could also pull in six. This change also required a change in the way generated proto code is imported in the channelz and health-check modules, as well as in their associated tests. We were importing them two different ways, each relative. This resulted in two different module objects being imported into the process, which were incompatible. I am not sure exactly what caused this behavior to begin, as this should have been possible before this PR. As a workaround, I am simply trying two different absolute imports and using the one that works. This should function both inside and outside of Bazel environments. 5 years ago			`py_library(`
			`name = "futures",`
			`srcs = glob(["concurrent/*/.py"]),`
			`srcs_version = "PY2AND3",`
			`visibility = ["//visibility:public"],`
			`)`