Lines Matching +full:python +full:- +full:test
5 Enable Building of gRPC Python with Bazel
9 gRPC Python currently has a constellation of scripts written to build the
11 [Bazel](https://bazel.build/) is the open-sourced variant of Google's internal
14 development, especially in terms of Python (amongst a few other languages).
16 The project aimed to fill this gap and build gRPC Python with Bazel.
20 …storage.googleapis.com/summerofcode-prod.appspot.com/gsoc/core_project/doc/5316764725411840_152204…
24 ### State of Bazel for Python
28 rules for Python are currently being separated out into their own repo at
32 Python](https://groups.google.com/forum/#!topic/bazel-sig-python/iQjV9sfSufw)
33 though. There's still challenges when it comes to building for Python 2 vs 3.
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
53 for Python. Hence, a fork of this repo was made and is to be used with gRPC
60 on their side. The way it works is by including Cython as a third-party Bazel
64 ### Packaging Python code using Bazel
66 pip and PyPI still remain the de-facto standard for distributing Python
70 there's no way yet to build Python packages for distribution.
72 ### Building gRPC Python with Bazel on Kokoro (internal CI)
78 to install the required dependencies (which were python-dev and Bazel) and a
79 new configuration file which pointed to the subdirectiory (src/python) under
82 ### Handling imports in Python code
84 When writing Python packages, imports in nested modules are typically made
87 a nifty `imports` parameter to all the Python rules which lets us specify for
91 ### Fetching Python headers for Cython code to use
93 Cython code makes use of `Python.h`, which pulls in the Python API for C
94 extension modules to use, but it's location depending on the Python version and
96 Tensorflow wrote [repository rules for Python
99 modifications](https://github.com/grpc/grpc/pull/15992) for use in gRPC Python
104 All the Bazel tests for gRPC Python can be run using a single command:
107 bazel test --spawn_strategy=standalone --genrule_strategy=standalone //src/python/...
110 If any specific test is to be run, like say `LoggingPoolTest` (which is present
112 `src/python/grpcio_tests/tests/unit/framework/foundation/_logging_pool_test.py`),
116 bazel test --spawn_strategy=standalone --genrule_strategy=standalone //src/python/grpcio_tests/test…
119 where, `logging_pool_test` is the name of the Bazel target for this test.
124 bazel test --spawn_strategy=standalone --genrule_strategy=standalone //src/python/grpcio_tests/test…
129 - Use `bazel build` with a `-s` flag to see the logs being printed out to
131 - Similarly, use `bazel test` with a `--test_output=streamed` to see the
132 test logs while testing. Something to know while using this flag is that all
139 - [435c6f8](https://github.com/grpc/grpc/commit/435c6f8d1e53783ec049b3482445813afd8bc514)
141 - [74426fd](https://github.com/grpc/grpc/commit/74426fd2164c51d6754732ebe372133c19ba718c)
143 - [b6518af](https://github.com/grpc/grpc/commit/b6518afdd610f0115b42aee1ffc71520c6b0d6b1)
145 - [ebcf04d](https://github.com/grpc/grpc/commit/ebcf04d075333c42979536c5dd2091d363f67e5a)
146 Kokoro setup for building gRPC Python with Bazel
147 - [3af1aaa](https://github.com/grpc/grpc/commit/3af1aaadabf49bc6274711a11f81627c0f351a9a)
148 Basic setup to build gRPC Python with Bazel
149 - [11f199e](https://github.com/grpc/grpc/commit/11f199e34dc416a2bd8b56391b242a867bedade4)
150 Workspace changes to build gRPC Python with Bazel
151 - [848fd9d](https://github.com/grpc/grpc/commit/848fd9d75f6df10f00e8328ff052c0237b3002ab)
152 Minimal Bazel BUILD files for grpcio Python
156 - [89ce16b](https://github.com/grpc/grpc/commit/89ce16b6daaad4caeb1c9ba670c6c4b62ea1a93c)
157 Update Dockerfiles for python artifacts to use latest git version
158 - [32f7c48](https://github.com/grpc/grpc/commit/32f7c48dad71cac7af652bf994ab1dde3ddb0607)
159 Revert removals from python artifact dockerfiles
160 - [712eb9f](https://github.com/grpc/grpc/commit/712eb9ff91cde66af94e8381ec01ad512ed6d03c)
162 - [c6e4372](https://github.com/grpc/grpc/commit/c6e4372f8a93bb0eb996b5f202465785422290f2)
163 Create README for gRPC Python reflection package
164 - [2e113ca](https://github.com/grpc/grpc/commit/2e113ca6b2cc31aa8a9687d40ee1bd759381654f)
165 Update logging in Python to use module-level logger
169 - BUILD files for all tests in
170 …com/ghostwriternr/grpc/blob/70c8a58b2918a5369905e5a203d7ce7897b6207e/src/python/grpcio_tests/tests…
171 - BUILD files for gRPC testing, gRPC health checking, gRPC reflection.
172 - (Yet to complete) BUILD files for grpcio_tools. One test depends on this.
176 - [grpc/grpc #16336](https://github.com/grpc/grpc/issues/16336) RuntimeError
177 for `_reconnect_test` Python unit test with Bazel
178 - Some tests in Bazel pass despite throwing an exception. Example:
180 `src/python/grpcio_tests/tests/unit/_metadata_code_details_test.py`.
181 - [#14557](https://github.com/grpc/grpc/pull/14557) introduced a minor bug
183 - Sanity test doesn't make sense in the context of Bazel, and thus fails.
184 - There are some issues with Python2 vs Python3. Specifically,
185 - On some machines, “cygrpc.so: undefined symbol: _Py_FalseStruct” error
186 shows up. This is because of incorrect Python version being used to build
188 - Some external packages like enum34 throw errors when used with Python 3 and
189 some extra packages are currently installed as Python version in current