First of all, I have an important naming question: what do you think of the name of the functions "link_future(future)" and "wrap_greenthread(greenthread)"?
- link_future() function: wait for a future from a greenthread. - wrap_greenthread() function: wrap a greenthread into a Future Can you maybe suggest better names? I hesitate to rename link_future() to wait_future(). It will be used as aiogreen.wait_future(), but it looks like asyncio.wait() and asyncio.wait_for(). 2014-11-19 15:20 GMT+01:00 Victor Stinner <[email protected]>: > Hi, I wrote a new project called "aiogreen": (..) Release early, release often! I just released aiogreen 0.2. I almost rewrote the project from scratch. It has a new implementation, unit tests and a documentation: http://aiogreen.readthedocs.org/ Later it would be nice to extract tests which are not specific to eventlet to build a test suite to validate any implementation of asyncio: test trollius, tulip, asyncio, aiogreen, etc. > The first release 0.1 lacks some features: networking, pipes and so > subprocesses, and signal handlers are not supported yet. Basically, all asyncio features are now supported. I reduced the code specific to eventlet to the minimum, so aiogreen is almost fully based on asyncio/trollius. In addition, it's also now possible to wait for a greenthread in a coroutine, and wait for a future or a task in a greenthread: http://aiogreen.readthedocs.org/using.html#api Waiting for a greenthread in a coroutine is the main feature of greenio. So aiogreen became a superset of greenio if I understood correctly. The implementations of aiogreen and greenio are completly different. aiogreen now works with eventlet when monkey-patching is used. Full changelog: http://aiogreen.readthedocs.org/changelog.html Victor
