Chiebot-Mirror/grpc - grpc - Gitea: Git with a cup of tea

Commit Graph

Author	SHA1	Message	Date
Richard Belleville	69f990673f	Conform to protobuf's usage of six	5 years ago
Lidi Zheng	c34bef4ca4	Format all Bazel files with buildifier	5 years ago
Jan Tattermusch	0460b9bb4b	fixup	5 years ago
Jan Tattermusch	b77cb8ae7c	replace git_repository occurence by http_archive	5 years ago
Richard Belleville	1444cd1dd3	Revert "Revert "Merge pull request #20097 from gnossen/dual_version_python_tests"" This reverts commit `24c562dbaa`.	5 years ago
Richard Belleville	24c562dbaa	Revert "Merge pull request #20097 from gnossen/dual_version_python_tests" This reverts commit `c9c847f334`, reversing changes made to `07ba4de392`.	5 years ago
Richard Belleville	426450cd82	Implement dual testing	5 years ago
Richard Belleville	7b2c8c27b0	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
Richard Belleville	930cec4e27	Revert "Merge pull request #18912 from grpc/revert-bazel-changes" This reverts commit `c9a259aa3a`, reversing changes made to `9c882bc725`.	6 years ago
Richard Belleville	50b5240d0a	Revert "Merge pull request #18859 from grpc/internal_py_proto_library" This reverts commit `5b720f19c1`, reversing changes made to `a64ae3c0d5`.	6 years ago
Richard Belleville	05f37c8143	Remove dependency on pubref/rules_proto. This commit resolves #18331. This commit resolves #18256. This commit resolves... another TODO that apparently didn't have an associated github issue. We swap out pubref's implementation of py_proto_library with our own, which more closely mirrors the interface of the internal py_proto_library, taking the descriptor file output of a proto_library rule as input. One minor change in behavior was introduced for simplicity. When a py_proto_library depends on a proto_library with a source proto file in a subdirectory of the bazel package, the import module of the resultant python library will reflect the package, not the full directory of the proto file, including both the bazel package and the subdirectories, as pubref did previously. This behavior also more closely mirrors google internal behavior. This commit also introduces a slightly more stringent bazel format script. Buildifier on its own will not take care of long lines, but by running yapf first, we end up with a more legible file. At the moment, there is no sanity check associated with this formatter.	6 years ago
Richard Belleville	f3f6237e6d	Wrap long line	6 years ago
Richard Belleville	615c95ed5c	Mitigate #18256	6 years ago

13 Commits (9e58d0645b5156891abbc33b504ead656871b0f0)