From 2ec1d0aeb5503188169c9cd7992b8db4a6472365 Mon Sep 17 00:00:00 2001 From: Lidi Zheng Date: Tue, 27 Aug 2019 10:45:50 -0700 Subject: [PATCH] Remove the python/async folder - This effort is already carried on in grpc/grpc. --- python/async/README.md | 25 ------------------------- 1 file changed, 25 deletions(-) delete mode 100644 python/async/README.md diff --git a/python/async/README.md b/python/async/README.md deleted file mode 100644 index 0a4c455..0000000 --- a/python/async/README.md +++ /dev/null @@ -1,25 +0,0 @@ -# Asynchronous gRPC Python - -We intend to support use of gRPC Python in use cases involving asynchronous frameworks, libraries, and language features. - -## Requirements - -* Straightforward, attractive, idiomatic developer-user story for using gRPC Python with [the `async`/`await` syntax introduced in Python 3.5](https://docs.python.org/3/whatsnew/3.5.html#pep-492-coroutines-with-async-and-await-syntax). -* Straightforward, attractive, idiomatic developer-user story for using gRPC Python with [the `asyncio` module introduced in Python 3.4](https://docs.python.org/3/whatsnew/3.4.html#asyncio) or a confident answer about why gRPC Python and `asyncio` needn't be used together or do not conflict. -* A not-too-painful developer-user story for using gRPC Python in 2.7-and-3.4+ with popular third-party asynchronous frameworks and libraries including - * [`gevent`](http://www.gevent.org) - * [`tornado`](http://www.tornadoweb.org/en/stable/) - * More? -* Unit test coverage of all supported behaviors introduced to gRPC Python. - -## Example application code - -When using gRPC Python with Python 3.5+, invoking fifty concurrent RPCs should look like -``` -# Well, what? -``` - -When using gRPC Python with Python 2.7 and `gevent`, invoking an RPC should look like -``` -# Well? -```