document using gevent for async

docs/deploying/eventlet.rst

@@ -1,80 +1,8 @@
+:orphan:
+
 eventlet
 ========
 
-Prefer using :doc:`gunicorn` with eventlet workers rather than using
-`eventlet`_ directly. Gunicorn provides a much more configurable and
-production-tested server.
+`Eventlet is no longer maintained.`__ Use :doc:`/deploying/gevent` instead.
 
-`eventlet`_ allows writing asynchronous, coroutine-based code that looks
-like standard synchronous Python. It uses `greenlet`_ to enable task
-switching without writing ``async/await`` or using ``asyncio``.
-
-:doc:`gevent` is another library that does the same thing. Certain
-dependencies you have, or other considerations, may affect which of the
-two you choose to use.
-
-eventlet provides a WSGI server that can handle many connections at once
-instead of one per worker process. You must actually use eventlet in
-your own code to see any benefit to using the server.
-
-.. _eventlet: https://eventlet.net/
-.. _greenlet: https://greenlet.readthedocs.io/en/latest/
-
-
-Installing
-----------
-
-When using eventlet, greenlet>=1.0 is required, otherwise context locals
-such as ``request`` will not work as expected. When using PyPy,
-PyPy>=7.3.7 is required.
-
-Create a virtualenv, install your application, then install
-``eventlet``.
-
-.. code-block:: text
-
-    $ cd hello-app
-    $ python -m venv .venv
-    $ . .venv/bin/activate
-    $ pip install .  # install your application
-    $ pip install eventlet
-
-
-Running
--------
-
-To use eventlet to serve your application, write a script that imports
-its ``wsgi.server``, as well as your app or app factory.
-
-.. code-block:: python
-    :caption: ``wsgi.py``
-
-    import eventlet
-    from eventlet import wsgi
-    from hello import create_app
-
-    app = create_app()
-    wsgi.server(eventlet.listen(("127.0.0.1", 8000)), app)
-
-.. code-block:: text
-
-    $ python wsgi.py
-    (x) wsgi starting up on http://127.0.0.1:8000
-
-
-Binding Externally
-------------------
-
-eventlet should not be run as root because it would cause your
-application code to run as root, which is not secure. However, this
-means it will not be possible to bind to port 80 or 443. Instead, a
-reverse proxy such as :doc:`nginx` or :doc:`apache-httpd` should be used
-in front of eventlet.
-
-You can bind to all external IPs on a non-privileged port by using
-``0.0.0.0`` in the server arguments shown in the previous section.
-Don't do this when using a reverse proxy setup, otherwise it will be
-possible to bypass the proxy.
-
-``0.0.0.0`` is not a valid address to navigate to, you'd use a specific
-IP address in your browser.
+__ https://eventlet.readthedocs.io

docs/deploying/gevent.rst

@@ -7,15 +7,12 @@ configurable and production-tested servers.
 
 `gevent`_ allows writing asynchronous, coroutine-based code that looks
 like standard synchronous Python. It uses `greenlet`_ to enable task
-switching without writing ``async/await`` or using ``asyncio``.
-
-:doc:`eventlet` is another library that does the same thing. Certain
-dependencies you have, or other considerations, may affect which of the
-two you choose to use.
+switching without writing ``async/await`` or using ``asyncio``. This is
+not the same as Python's ``async/await``, or the ASGI server spec.
 
 gevent provides a WSGI server that can handle many connections at once
-instead of one per worker process. You must actually use gevent in your
-own code to see any benefit to using the server.
+instead of one per worker process. See :doc:`/gevent` for more
+information about enabling it in your application.
 
 .. _gevent: https://www.gevent.org/
 .. _greenlet: https://greenlet.readthedocs.io/en/latest/
@@ -24,8 +21,7 @@ own code to see any benefit to using the server.
 Installing
 ----------
 
-When using gevent, greenlet>=1.0 is required, otherwise context locals
-such as ``request`` will not work as expected. When using PyPy,
+When using gevent, greenlet>=1.0 is required. When using PyPy,
 PyPy>=7.3.7 is required.
 
 Create a virtualenv, install your application, then install ``gevent``.

docs/deploying/gunicorn.rst

@@ -8,7 +8,7 @@ multiple worker implementations for performance tuning.
 *   It does not support Windows (but does run on WSL).
 *   It is easy to install as it does not require additional dependencies
     or compilation.
-*   It has built-in async worker support using gevent or eventlet.
+*   It has built-in async worker support using gevent.
 
 This page outlines the basics of running Gunicorn. Be sure to read its
 `documentation`_ and use ``gunicorn --help`` to understand what features
@@ -93,20 +93,19 @@ otherwise it will be possible to bypass the proxy.
 IP address in your browser.
 
 
-Async with gevent or eventlet
------------------------------
+Async with gevent
+-----------------
 
-The default sync worker is appropriate for many use cases. If you need
-asynchronous support, Gunicorn provides workers using either `gevent`_
-or `eventlet`_. This is not the same as Python's ``async/await``, or the
-ASGI server spec. You must actually use gevent/eventlet in your own code
-to see any benefit to using the workers.
+The default sync worker is appropriate for most use cases. If you need numerous,
+long running, concurrent connections, Gunicorn provides an asynchronous worker
+using `gevent`_. This is not the same as Python's ``async/await``, or the ASGI
+server spec. See :doc:`/gevent` for more information about enabling it in your
+application.
 
-When using either gevent or eventlet, greenlet>=1.0 is required,
-otherwise context locals such as ``request`` will not work as expected.
-When using PyPy, PyPy>=7.3.7 is required.
+.. _gevent: https://www.gevent.org/
 
-To use gevent:
+When using gevent, greenlet>=1.0 is required. When using PyPy, PyPy>=7.3.7 is
+required.
 
 .. code-block:: text
 
@@ -115,16 +114,3 @@ To use gevent:
     Listening at: http://127.0.0.1:8000 (x)
     Using worker: gevent
     Booting worker with pid: x
-
-To use eventlet:
-
-.. code-block:: text
-
-    $ gunicorn -k eventlet 'hello:create_app()'
-    Starting gunicorn 20.1.0
-    Listening at: http://127.0.0.1:8000 (x)
-    Using worker: eventlet
-    Booting worker with pid: x
-
-.. _gevent: https://www.gevent.org/
-.. _eventlet: https://eventlet.net/

docs/deploying/index.rst

@@ -36,7 +36,6 @@ discusses platforms that can manage this for you.
     mod_wsgi
     uwsgi
     gevent
-    eventlet
     asgi
 
 WSGI servers have HTTP servers built-in. However, a dedicated HTTP

docs/deploying/uwsgi.rst

@@ -119,15 +119,16 @@ IP address in your browser.
 Async with gevent
 -----------------
 
-The default sync worker is appropriate for many use cases. If you need
-asynchronous support, uWSGI provides a `gevent`_ worker. This is not the
-same as Python's ``async/await``, or the ASGI server spec. You must
-actually use gevent in your own code to see any benefit to using the
-worker.
+The default sync worker is appropriate for most use cases. If you need numerous,
+long running, concurrent connections, uWSGI provides an asynchronous worker
+using `gevent`_. This is not the same as Python's ``async/await``, or the ASGI
+server spec. See :doc:`/gevent` for more information about enabling it in your
+application.
 
-When using gevent, greenlet>=1.0 is required, otherwise context locals
-such as ``request`` will not work as expected. When using PyPy,
-PyPy>=7.3.7 is required.
+.. _gevent: https://www.gevent.org/
+
+When using gevent, greenlet>=1.0 is required. When using PyPy, PyPy>=7.3.7 is
+required.
 
 .. code-block:: text
 
@@ -140,6 +141,3 @@ PyPy>=7.3.7 is required.
     spawned uWSGI worker 1 (pid: x, cores: 100)
     spawned uWSGI http 1 (pid: x)
     *** running gevent loop engine [addr:x] ***
-
-
-.. _gevent: https://www.gevent.org/