blazespinnaker

Ah, ok I see the confusion: "My sleep above uses run, which I assumed (wrongly I guess) that it would turn control over to the event_loop similar to what happens...

fwiw, this causes starvation as well: ``` async def sleepAsync(x): await asyncio.sleep(x) def sleep(x): asyncio.run(sleepAsync(x)) ``` As I mentioned above, I believe that the nested run is not using the...

The problem that I see with this library is your run into things like this: https://stackoverflow.com/questions/57639751/how-to-fix-runtime-error-cannot-close-a-running-event-loop-python-discord-bot Where the sypder maintainer is suggesting to run the patch. Better would be just...

> > The latter unpatched approach runs as expected. > > Perhaps, I think the behavior you see is what I would expect, unless I knew sleep was monkey-patched. >...

> @blazespinnaker: > > > ...or at at the very least it's not slicing out time to tasks already scheduled on it. > > Just like plain asyncio, gevent, lua,...

Btw, I am confused by this statement: ...or at at the very least it's not slicing out time to tasks already scheduled on it. _Just like plain asyncio, gevent, lua,...

> > I am claiming that nested run calls with this library will not execute tasks scheduled before the nested run call. > > If true, can you show failure...

Here's another example - https://github.com/pyppeteer/pyppeteer/issues/99

Going to submit a bug on python.org, but I thought it'd make sense to give @erdewit the opportunity to address it here first. Contents as follows: "I'm seeing a high...

I think this would be exceedingly useful, not only to better understand the behavior but also to potentially alter it. For the latter, hooks would be the best place to...