Project: gRPC (Orchestration & Management / Remote Procedure Call)
File: naresh.md

Enable Building of gRPC Python with Bazel gRPC Python currently has a constellation of scripts written to build the project, but it has a lot of limitations in terms of speed and maintainability. is the open-sourced variant of Google's internal system, Blaze, which is an ideal replacement for building such projects in a fast and declarative fashion. But Bazel in itself is still in active development, especially in terms of Python (amongst a few other languages). The project aimed to fill this gap and build gRPC Python with Bazel. Although previously speculated, the project didn't require any contributions directly to . The Bazel rules for Python are currently being separated out into their own repo at . Bazel is [still very much in active development for Python](https://groups.google.com/forum/#!topic/bazel-sig-python/iQjV9sfSufw) though. There's still challenges when it comes to building for Python 2 vs 3. Using pip packages is still in experimental. Bazel Python support is currently distributed across these two repositories and is yet to begin migration to one place (which will be ). Bazel's roadmap for Python is publicly available [here as a Google doc](https://docs.google.com/document/d/1A6J3j3y1SQ0HliS86mZBnB5UeBe7vExWL2RydEONI/edit). Cross contribution surprisingly came up because of building protobuf sources for Python, which is still not natively supported by Bazel. An existing repository, , which was maintained by an independent maintainer (i.e. not a part of Bazel) helped solve this problem, but had [one major blocking issue](https://github.com/pubref/rules_protobuf/issues/233) and could not be resolved at the source. But [a solution to the issue](https://github.com/pubref/rules_protobuf/pull/196) was proposed by user dududko, which was not merged because of failing golang tests but worked well for Python. Hence, a fork of this repo was made and is to be used with gRPC until the solution can be merged back at the source. Building Cython code is still not supported by Bazel, but the team at have added support for Bazel on their side. The way it works is by including Cython as a third-party Bazel dependency and using custom Bazel rules for building our Cython code using the binary within the dependency. pip and PyPI still remain the de-facto standard for distributing Python packages. Although Bazel is pretty versatile and is amazing for it's reproducible and incremental build capabilities, these can only be still used by the contributors and developers for building and testing the gRPC code. But there's no way yet to build Python packages for distribution. Integration with the internal CI was one of the areas that highlighted how simple Bazel can be to use. gRPC was already using a dockerized Bazel setup to build some of it's core code (but not as the primary build setup). Adding a new job on the internal CI ended up being as simple as creating a new shell script to install the required dependencies (which were python-dev and Bazel) and a new configuration file which pointed to the subdirectiory (src/python) under which to look for targets and run the tests

When writing Python packages, imports in nested modules are typically made relative to the package root. But because of the way Bazel works, these paths wouldn't make sense from the Workspace root. So, the folks at Bazel have added a nifty `imports` parameter to all the Python rules which lets us specify for each target, which path to consider as the root. This parameter allows for relative paths like `imports = ["../",]`. Cython code makes use of `Python.h`, which pulls in the Python API for C extension modules to use, but it's location depending on the Python version and operating system the code is building on. To make this easier, the folks at Tensorflow wrote [repository rules for Python autoconfiguration](https://github.com/tensorflow/tensorflow/tree/e447ae4759317156d31a9421290716f0ffbffcd8/third_party/py). This has been [adapted with some some modifications](https://github.com/grpc/grpc/pull/15992) for use in gRPC Python as well. All the Bazel tests for gRPC Python can be run using a single command: ```bash bazel test --spawnstrategy=standalone --genrulestrategy=standalone //src/python/... ``` If any specific test is to be run, like say `LoggingPoolTest` (which is present in `src/python/grpciotests/tests/unit/framework/foundation/loggingpooltest.py`), the command to run would be: ```bash bazel test --spawnstrategy=standalone --genrulestrategy=standalone //src/python/grpciotests/tests/unit/framework/foundation:loggingpool_test ``` where, `loggingpooltest` is the name of the Bazel target for this test. Similarly, to run a particular method, use: ```bash bazel test --spawnstrategy=standalone --genrulestrategy=standalone //src/python/grpciotests/tests/unit/rpctest --testarg=RPCTest.testUnrecognizedMethod ``` Use `bazel build` with a `-s` flag to see the logs being printed out to standard output while building. Similarly, use `bazel test` with a `--test_output=streamed` to see the test logs while testing. Something to know while using this flag is that all tests will be run locally, without sharding, one at a time. Update grpc_gevent cython files to include .pxi Add geventutil.h to grpcbase_c Bazel target Upgrade Bazel to 0.15.0 Kokoro setup for building gRPC Python with Bazel Basic setup to build gRPC Python with Bazel Workspace changes to build gRPC Python with Bazel Minimal Bazel BUILD files for grpcio Python Update Dockerfiles for python artifacts to use latest git version Revert removals from python artifact dockerfiles Make logging after success in jobset more apparent Create README for gRPC Python reflection package Update logging in Python to use module-level logger BUILD files for all tests in . BUILD files for gRPC testing, gRPC health checking, gRPC reflection. (Yet to complete) BUILD files for grpcio_tools. One test depends on this. RuntimeError for `reconnecttest` Python unit test with Bazel Some tests in Bazel pass despite throwing an exception. Example: `testAbortedStreamStream` in `src/python/grpciotests/tests/unit/metadatacodedetails_test.py`. introduced a minor bug where the module level loggers don't initialize a default logging handler. Sanity test doesn't make sense in the context of Bazel, and thus fails. There are some issues with Python2 vs Python3. Specifically, On some machines, cygrpc.so: undefined symbol: PyFalseStruct error shows up. This is because of incorrect Python version being used to build Cython. Some external packages like enum34 throw errors when used with Python 3 and some extra packages are currently installed as Python version in current build scripts. For now, the extra packages are added to a `requirements.bazel.txt` file in the repository root.