RETIRED, further work has moved to Debian project infrastructure
Go to file
Victor Stinner 5c28a55e01 add a setup.py 2014-11-19 03:10:45 +01:00
.hgignore initial commit 2014-11-07 15:16:57 +01:00
README add a setup.py 2014-11-19 03:10:45 +01:00
aiogreen.py rename aiogreen/__init__.py to aiogreen.py 2014-11-19 03:03:23 +01:00
setup.py add a setup.py 2014-11-19 03:10:45 +01:00

README

asyncio event loop scheduling callbacks in eventlet.

See also the Trollius project:
http://trollius.readthedocs.org/

Status
------

The version 0.1 is the first public release. It was not tested on any project
yet.


Installation
------------

Requirements:

- eventlet (it was tested with eventlet 0.15)
- trollius 1.0 or newer

Type::

    pip install aiogreen

or::

    python setup.py install


Implemented
-----------

* call_at()
* call_later()
* call_soon()
* run_forever()
* run_in_executor()
* run_until_complete()
* stop()
* coroutines and tasks


Not supported (yet)
-------------------

* run an event loop in a thread different than the main thread
* sockets: create_connection, create_server, sock_recv
* pipes: connect_read_pipe
* subprocesses: need pipes
* signal handlers: add_signal_handler (only for pyevent hub?)


To do
-----

* Write new unit tests, or split Tulip test suite between implementation tests
  and specification tests
* Support eventlet without monkey-patching
* Test with Python 2 and 3
* Test with Trollius and asyncio
* Glue to ease debug: keep traceback between Handle, coroutine and greenthread.
  Is it even possible?
* run_in_executor(): use eventlet.tpool as the default executor?
  It avoids the dependency to concurrent.futures. aiogreen is written as a
  temporary solution to switch from eventlet to asyncio. So it may be better to
  use directly concurrent.futures to reduce the usage of eventlet?