Chiebot-Mirror
/
grpc
mirror of https://github.com/grpc/grpc.git
8
0
Fork 0
Code Issues Projects Releases Wiki Activity
The C based gRPC (C++, Python, Ruby, Objective-C, PHP, C#) https://grpc.io/
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
51181 Commits
280 Branches
379 Tags
1.3 GiB
Tag: Branch: Tree: 7976501534
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '7976501534'
${ noResults }
grpc/test/distrib/bazel/python/WORKSPACE

23 lines
480 B
Raw Normal View History Unescape

Add bazel cpp distribtest for grpc_cc_library (#29175) * Add bazel cpp distribtest for grpc_cc_library * Add new directory to bazelignore * Try changing to workspace differently * Debug cd * Fix bazel wrapper * Yet more debug * Try again * Clean up * Sanity fixes * Run per-language distribtests even if overall build fails
3 years ago
# TODO: Move to test/distrib/python.
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
local_repository(
name = "com_github_grpc_grpc",
Rehome python bazel distribtest (#29275) * WIP * Test multiple languages * Yapf * isort * Shellcheck * comment not provided * Fix import ordering issue. * Turn up Bazel logging
3 years ago
path = "../../../..",
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_proto_library uses workspace and pkg paths All python imports currently are added to the runfiles under __main__ which is only the default when no workspace name is provided. This change supports both empty workspace names, and specified workspace names. This also supports python libs not anchored at root
5 years ago
# Ensure rules don't rely on __main__ naming convention.
workspace(name = "python_test_repo")
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
load("@com_github_grpc_grpc//bazel:grpc_deps.bzl", "grpc_deps")
Add protobuf_deps to python_test_repo WORKSPACE
5 years ago
Address comments. - Fix sanit test check_bazel_workspace.py. - Use the new `grpc_extra_deps` in the Bazel workspace test.
5 years ago
grpc_deps()
Compensate for missing upb dependencies
5 years ago
Address comments. - Fix sanit test check_bazel_workspace.py. - Use the new `grpc_extra_deps` in the Bazel workspace test.
5 years ago
load("@com_github_grpc_grpc//bazel:grpc_extra_deps.bzl", "grpc_extra_deps")
AAAAAAAHHHHHH
5 years ago
Address comments. - Fix sanit test check_bazel_workspace.py. - Use the new `grpc_extra_deps` in the Bazel workspace test.
5 years ago
grpc_extra_deps()
[bazel] Fix import path for virtual packages (#28103) This change moves the logic for computing the package name part of an import directory from python_rules.bzl to protobuf.bzl, and reinstates the workspace root part of the directory. The effect is that it is now possible for a py_library_rule to depend on a proto_library in a different repository whose source files are generated.
3 years ago
local_repository(
name = "some_other_repo",
path = "../python_second_test_repo",
)