Joshua Moore-Oliva added the comment:
Also - should I close this issue now that a patch has been committed?
--
___
Python tracker
<http://bugs.python.org/issue22
Joshua Moore-Oliva added the comment:
> Hm. That sounds like you won't actually be interoperable with other
> asyncio-using code.
asyncio code can be interoperated with by spinning off an asyncio coroutine
that on completion calls a callback that reschedules a non-asyncio coroutine
Changes by Joshua Moore-Oliva :
--
nosy: +chatgris
___
Python tracker
<http://bugs.python.org/issue21965>
___
___
Python-bugs-list mailing list
Unsubscribe:
Joshua Moore-Oliva added the comment:
> I will try to review later tonight.
Thanks!
> That makes sense when using gevent, but not when using asyncio or Trollius.
> Nothing will make events run if you don't use yield [from].
Yes, I am aware of that. I have written a small custom
Joshua Moore-Oliva added the comment:
My patch is ready for review, if I followed the process correctly I think you
should have received an email
https://codereview.appspot.com/145220043
> By the way I just looked at wait_for.py; it has a bug where do_work() isn't
> using yield-fr
Joshua Moore-Oliva added the comment:
> You can contribute upstream to the Tulip project first.
Will I be writing a patch and tests for tulip, and then separate a patch and
tests for python 3.4? Or will I submit to tulip, and then the changes will get
merged from tulip into python by s
New submission from Joshua Moore-Oliva:
The core issue stems from the implementation of Timer cancellation. (which
features like asyncio.wait_for build upon). BaseEventLoop stores scheduled
events in an array backed heapq named _scheduled. Once an event has been
scheduled with call_at
