Library can not be used in an existing asyncio event loop

[akshualy]

In the current implementation I receive a RuntimeError: asyncio.run() cannot be called from a running event loop because of the _async_helper in client.py.

It would be nice to have an alternative version where the existing async context is used, maybe by providing public async methods.

My current workaround was to reimplement the existing methods, so there is no urgency.

[opulentfox-29]

In the future i plan to rewrite the library to be asynchronous. I tried using asyncio.get_event_loop().create_task() but it didn't work, it will wait for the nearest await to execute the task.

My current workaround was to reimplement the existing methods

The library has more encryption than requests, a simple async\await implementation will not allow you to execute code asynchronously, once the code reaches encryption, all your coroutines will wait for synchronous encryption.

Use await asyncio.to_thread() instead, this will allow you to do all synchronous operations in a separate CPU thread and allow the library to use asyncio.run() in a running event loop

[iliarusskikh]

I have encountered the same issue when I was implementing protonmail MCP client, and came up with the following solution/example:

await run_in_thread(proton.save_session, 'session.pickle')

async def run_in_thread(func, *args, **kwargs):
"""
Run a synchronous function in a separate thread to avoid blocking the event loop.
Supports both positional and keyword arguments.
"""
return await asyncio.to_thread(partial(func, *args, **kwargs))

Hope it helps for the future developers. Many thanks to contributors