grpc/requirements.bazel.txt

# GRPC Python setup requirements
coverage==4.5.4
cython==0.29.21
enum34==1.1.10
protobuf>=3.5.0.post1, < 4.0dev
wheel==0.36.2
futures==3.1.1
google-auth==1.24.0
oauth2client==4.1.0
requests==2.25.1
urllib3==1.26.5
chardet==3.0.4
certifi==2017.4.17
idna==2.7
googleapis-common-protos==1.5.5
gevent==21.12.0
zope.event==4.5.0
setuptools==44.1.1
xds-protos==0.0.11
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`
Pin all Bazel pypi dependencies 4 years ago			`coverage==4.5.4`
			`cython==0.29.21`
			`enum34==1.1.10`
Set version upper bound for protobuf; installs grpcio-tools instead 5 years ago			`protobuf>=3.5.0.post1, < 4.0dev`
Pin all Bazel pypi dependencies 4 years ago			`wheel==0.36.2`
			`futures==3.1.1`
			`google-auth==1.24.0`
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			`oauth2client==4.1.0`
Pin all Bazel pypi dependencies 4 years ago			`requests==2.25.1`
Bump bazel urllib3 version to 1.26.5 (#26402) 4 years ago			`urllib3==1.26.5`
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`
upgrade gevent version in bazel requirement (#31115) 2 years ago			`gevent==21.12.0`
Create Bazel gevent test harness (#27507) * WIP * Add gevent test suite run under Bazel. * Fix things up * Yapf * Fix up Bazel files * Make py_grpc_test fancier * Attempt to fix Windows RBE * Attempt to kick GitHub * Fix Python 2 runs * Yet more fixes * And the patch file too * I am an idiot * Mark gevent tests flaky * Try to make rules_python more tolerant * Typo * Exclude reconnect test from gevent * Remove unnecessary parts of patch * Buildifier * You saw nothing * isort * Move py_grpc_test to an internal-only file * Review comments * More reviewer comments * Review 3 years ago			`zope.event==4.5.0`
			`setuptools==44.1.1`
[xDS Proto] Remove Python's usage of copied proto files (#29516) 3 years ago			`xds-protos==0.0.11`