11 Commity (dd80d188661ed8da87935c30051973a9370e1b99)

Autor	SHA1	Wiadomość	Data
Paul Sokolovsky	dd80d18866	asyncio_slow: Add example of wait() from docs.	2014-10-11 05:19:50 +03:00
Paul Sokolovsky	be628acf7d	asyncio_slow: Fix wait: again, should not schedule anything itself.	2014-10-11 05:19:50 +03:00
Paul Sokolovsky	96cbb50e27	asyncio_slow: Add Future examples from docs.	2014-10-11 05:19:50 +03:00
Paul Sokolovsky	8711a45a13	asyncio_slow: Implement loop.stop().	2014-10-11 05:19:50 +03:00
Paul Sokolovsky	3a639ce666	asyncio_slow: run_until_complete() should not schedule anyhing. ... Everything should be scheduled either already, or async() does this.	2014-10-11 05:19:50 +03:00
Paul Sokolovsky	6bff4dbe72	asyncio_slow: Add example on chaining coros using "yield from" from docs.	2014-10-11 05:19:50 +03:00
Paul Sokolovsky	6ded654afe	asyncio_slow: Add example for scheduling coro using Task.	2014-10-11 05:19:50 +03:00
Paul Sokolovsky	93178819b3	asyncio_slow: Add coroutine example from docs.	2014-10-11 05:19:50 +03:00
Paul Sokolovsky	b0c4fc7536	asyncio_slow: Add callback example from docs.	2014-10-11 05:19:50 +03:00
Paul Sokolovsky	1d7b189e75	asyncio_slow: Fix call_soon(), add call_later().	2014-10-11 05:19:50 +03:00
Paul Sokolovsky	5166ecbbd1	asyncio_slow: Start new upstream API-compatible asyncio implementation. ... The trait of this implementation is that it doesn't use priority queue and time scheduling, and instead does its all operations using polling, starting with such basic one as sleep. On the other hand, this tries to implement all (well, much) of upstream asyncio API and warts. asyncio_slow: Rename from asyncio_micro. It may turn out that this won't be "micro" at all. The main trait of this implementation is that it stay 100% API compatible with upstream (in those APIs which are implemented of course). It will also keep inefficient implementation of event loop scheduling, to discourage its use. Here we go.	2014-10-11 05:19:50 +03:00