grpc/requirements.bazel.txt

# GRPC Python setup requirements
coverage>=4.0
cython>=0.29.8
enum34>=1.0.4
protobuf>=3.5.0.post1
six>=1.10
wheel>=0.29
futures>=2.2.0
google-auth>=1.0.0
oauth2client==4.1.0
requests>=2.14.2
urllib3>=1.23
chardet==3.0.4
certifi==2017.4.17
idna==2.7
googleapis-common-protos==1.5.5
Workspace changes to build gRPC Python with Bazel - Include new rules from bazelbuild/rules_python, which allow for importing pip dependencies with Bazel. - Make Cython BUILD file visible to WORKSPACE. - Use a custom requirements file for Bazel python. This is added to allow for requirements previously added only during build steps. 6 years ago			`# GRPC Python setup requirements`
			`coverage>=4.0`
Bump up the Cython version to 0.29.8 6 years ago			`cython>=0.29.8`
Workspace changes to build gRPC Python with Bazel - Include new rules from bazelbuild/rules_python, which allow for importing pip dependencies with Bazel. - Make Cython BUILD file visible to WORKSPACE. - Use a custom requirements file for Bazel python. This is added to allow for requirements previously added only during build steps. 6 years ago			`enum34>=1.0.4`
			`protobuf>=3.5.0.post1`
			`six>=1.10`
			`wheel>=0.29`
			`futures>=2.2.0`
			`google-auth>=1.0.0`
			`oauth2client==4.1.0`
Bazel rules for gRPC Python interop tests Add interop tests for gRPC Python. py_proto_library rules are added to src/proto/grpc/testing/BUILD since grpc_proto_library is not compatible with py_* rules. 'requests' python module is added to requirements.bazel.txt as it is a dependency for google-auth. Previously, this was installed through tools/run_tests/helper_scripts/build_python.sh before running tests. 6 years ago			`requests>=2.14.2`
Update urllib3 to avoid security vulnerability 6 years ago			`urllib3>=1.23`
Add missing transitive dependencies This commit resolves an interop test currently failing on master. Over the past couple of weeks, bazel-based tests have been introduced. The current setup does not appear to automatically handle transitive dependencies. Instead, transitive dependencies such as `requests` have been manually added to `requirements.bazel.txt`. It appears that the build server happened to have the dependencies of the `requests` library installed already, but later had a configuration wipe. This was compounded by the google-auth library erroneously reporting that the `requests` module itself was not installed. In fact, it was the transitive dependencies of `requests` that were not being installed by the build file. (third-order dependencies of our test) I consider this a quick fix to get the build passing. In the long run, we need to automatically resolve and install transitive dependencies in our bazel builds. Resolves: #17170 6 years ago			`chardet==3.0.4`
			`certifi==2017.4.17`
			`idna==2.7`
Add grpcio-status extension package * The new package has 2 API `from_call` and `to_status` * Utilize the experimental API `abort_with_status` * Add 5 unit test cases 6 years ago			`googleapis-common-protos==1.5.5`