Lines Matching refs:Bazel
5 Enable Building of gRPC Python with Bazel
11 [Bazel](https://bazel.build/) is the open-sourced variant of Google's internal
13 fast and declarative fashion. But Bazel in itself is still in active
16 The project aimed to fill this gap and build gRPC Python with Bazel.
24 ### State of Bazel for Python
27 directly to [bazelbuild/bazel](https://github.com/bazelbuild/bazel). The Bazel
31 Bazel is [still very much in active development for
34 Using pip packages is still in experimental. Bazel Python support is currently
39 Bazel's roadmap for Python is publicly available [here as a Google
45 for Python, which is still not natively supported by Bazel. An existing
47 which was maintained by an independent maintainer (i.e. not a part of Bazel)
58 Building Cython code is still not supported by Bazel, but the team at
59 [cython/cython](https://github.com/cython/cython) have added support for Bazel
60 on their side. The way it works is by including Cython as a third-party Bazel
61 dependency and using custom Bazel rules for building our Cython code using the
64 ### Packaging Python code using Bazel
67 packages. Although Bazel is pretty versatile and is amazing for it's
72 ### Building gRPC Python with Bazel on Kokoro (internal CI)
75 simple Bazel can be to use. gRPC was already using a dockerized Bazel setup to
78 to install the required dependencies (which were python-dev and Bazel) and a
85 relative to the package root. But because of the way Bazel works, these paths
86 wouldn't make sense from the Workspace root. So, the folks at Bazel have added
104 All the Bazel tests for gRPC Python can be run using a single command:
119 where, `logging_pool_test` is the name of the Bazel target for this test.
127 ## Useful Bazel flags
142 Add gevent_util.h to grpc_base_c Bazel target
144 Upgrade Bazel to 0.15.0
146 Kokoro setup for building gRPC Python with Bazel
148 Basic setup to build gRPC Python with Bazel
150 Workspace changes to build gRPC Python with Bazel
152 Minimal Bazel BUILD files for grpcio Python
177 for `_reconnect_test` Python unit test with Bazel
178 - Some tests in Bazel pass despite throwing an exception. Example:
183 - Sanity test doesn't make sense in the context of Bazel, and thus fails.