What's your platform? kqueue backend fails on OSX 10.9. So some of my 
following observations might be due to a bug in the event loop 
implementation:

- test_futures: test_iter and test_yield_from_twice: yield instead of yield 
from has no effect if done without scheduler, so these tests should be 
obsolete. This means, that Future.__iter__ could be dropped, too.
- test_as_completed_with_timeout: the timed assertion might be due to the 
overhead of using tasks instead of "real" coroutines (AssertionError: 0.12 
!= 0.1 within 7 places). So you could just make this test less restrictive 
by using assertAlmostEqual(a, b, places=1). But I'm not sure, could be 
something else :)
- test_yield_vs_yield_from and test_yield_vs_yield_from_generator are 
completely nonsense because yielding a future should not raise a 
RuntimeError anymore (the former blocks infinitely on my system but I guess 
this is a bug in the event loop). [In original tulip yielding a Future 
raises RuntimeError to make sure that you never mix yield and yield from.]
- NameError in test_wait_for is obvious :) @asyncio.coroutine -> 
@tasks.coroutine
- test_task_repr_custom: there is a super() left



Reply via email to