unsync replaces event loop for main thread about unsync HOT 3 CLOSED

I made a PR for this: #8 but I'm concerned that this is not as simple as it seems, I'm curious to know in what cases the main thread's event loop possibly be used by an asyncio Future/coroutine that might be awaited by an @unsync function.

It appears that coroutines started in the main thread will still get executed in the event loop of the coroutine that awaits it. I'm pretty sure that means this change is safe, but I'm going to spend some more time looking into any other ways a coroutine/Future from asyncio could get executed in main thread's event loop while being awaited by an @unsync function.

from unsync.

I expect unsync to work in another thread with its own event loop and don't make a mess with main thread and loop. Don't know how to implement it. Any ideas?

from unsync.

It's ok that coroutine will get executed in the event loop of another coroutine that awaits it. But simple async functions that is not marked with @unsync decorator should not be executed in the unsync event loop. Here is what I mean in code:

async def async_coro_returning_event_loop() -> asyncio.AbstractEventLoop:
    await asyncio.sleep(0.001)
    loop = asyncio.get_event_loop()
    return loop

@unsync
async def unsync_coro_returning_event_loop() -> asyncio.AbstractEventLoop:
    return await async_coro_returning_event_loop()

main_loop = asyncio.get_event_loop()
unsync_loop = unsync.loop

assert main_loop != unsync_loop
assert main_loop == await async_coro_returning_event_loop()
assert unsync_loop == unsync_coro_returning_event_loop().result()

It seems that #8 fixes issue -- unsync does asyncio.set_event_loop in its own separate thread.

from unsync.