RETIRED, further work has moved to Debian project infrastructure
Go to file
Victor Stinner df7b72185c Added tag 0.5.1 for changeset 1c5b3f16c94d 2016-02-22 17:40:55 +01:00
doc 0.5.1: fix stop() 2016-02-22 17:23:39 +01:00
tests drop support for Python 2.6 and 3.2 2016-02-22 14:16:40 +01:00
.hgignore initial commit 2014-11-07 15:16:57 +01:00
.hgtags Added tag 0.5.1 for changeset 1c5b3f16c94d 2016-02-22 17:40:55 +01:00
COPYING add COPYING 2014-11-19 03:13:22 +01:00
MANIFEST.in MANIFEST.in: add run_aiotest.py 2014-12-18 13:25:32 +01:00
Makefile rename the project from aiogreen to aioeventlet 2014-12-03 00:28:13 +01:00
README rename the project from aiogreen to aioeventlet 2014-12-03 00:28:13 +01:00
aioeventlet.py 0.5.1: fix stop() 2016-02-22 17:23:39 +01:00
run_aiotest.py tox now also run the aiotest test suite 2014-12-12 18:03:43 +01:00
runtests.py runtests.py: add --monkey-patch/-m command line option 2014-11-19 23:17:56 +01:00
setup.py 0.5.1: fix stop() 2016-02-22 17:23:39 +01:00
tox.ini drop support for Python 2.6 and 3.2 2016-02-22 14:16:40 +01:00

README

aioeventlet implements the asyncio API (PEP 3156) on top of eventlet. It makes
possible to write asyncio code in a project currently written for eventlet.

aioeventlet allows to use greenthreads in asyncio coroutines, and to use
asyncio coroutines, tasks and futures in greenthreads: see ``link_future()``
and ``wrap_greenthread()`` functions.

The main visible difference between aioeventlet and trollius is the behaviour
of ``run_forever()``: ``run_forever()`` blocks with trollius, whereas it runs
in a greenthread with aioeventlet. It means that aioeventlet event loop can run
in an greenthread while the Python main thread runs other greenthreads in
parallel.

* `aioeventlet documentation <http://aioeventlet.readthedocs.org/>`_
* `aioeventlet project in the Python Cheeseshop (PyPI)
  <https://pypi.python.org/pypi/aioeventlet>`_
* `aioeventlet project at Bitbucket <https://bitbucket.org/haypo/aioeventlet>`_
* Copyright/license: Open source, Apache 2.0. Enjoy!