summaryrefslogtreecommitdiff
path: root/doc/threading.rst
diff options
context:
space:
mode:
authorSergey Shepelev <temotor@gmail.com>2018-02-17 22:41:37 +0300
committerSergey Shepelev <temotor@gmail.com>2018-03-11 02:21:01 +0300
commitfb300387a2f2761423dc71b3e4d18cb26a360368 (patch)
tree0dad33d1bf722f8701c5b919d658d3f559c06912 /doc/threading.rst
parent8fe75a76e773305f9748e3922aaf44bf4c39a939 (diff)
downloadeventlet-up.tar.gz
hubs: drop pyevent hubup
Diffstat (limited to 'doc/threading.rst')
-rw-r--r--doc/threading.rst2
1 files changed, 0 insertions, 2 deletions
diff --git a/doc/threading.rst b/doc/threading.rst
index 3a0486e..7e91db6 100644
--- a/doc/threading.rst
+++ b/doc/threading.rst
@@ -9,8 +9,6 @@ You can only communicate cross-thread using the "real" thread primitives and pip
The vast majority of the times you'll want to use threads are to wrap some operation that is not "green", such as a C library that uses its own OS calls to do socket operations. The :mod:`~eventlet.tpool` module is provided to make these uses simpler.
-The optional :ref:`pyevent hub <understanding_hubs>` is not compatible with threads.
-
Tpool - Simple thread pool
---------------------------