Eager tasks are a new feature and a library I have developed few years ago is not compatible with it. However, it would be nice if my code could coexist in one program with asyncio code using this feature. Lazy tasks for me, eager tasks for them, if they prefer.

Eager tasks are a new feature and a library I have developed few years ago is not compatible with it. However, it would be nice if my code could coexist in one program with asyncio code using this feature. Lazy tasks for me, eager tasks for them, if they prefer.

I am trying to build a batched queue processor with asyncio. The way it should work is that one should be able to push individual requests into the queue and that the queue processor would batch these up based on some heuristic, process the batch and that it would then release the results back to the calling tasks. That each calling task should be blocked/awaited until it’s result is available.

I have a manager script that’s launching some processes, then using two coroutines (one to monitor, one to gather results). For some reason only one coroutine seems to be run, what am I missing? (I don’t work with asyncio)

await loop.run_in_executor(executor, open_read) wont return untill await asyncio.shield(get_audio_async(sentance)) yields control to the event loop. I put in the await asyncio.sleep(0) calls to no avail. Any ideas?

import asyncio async def long_running_task(): try: while True: # Your long-running processing if asyncio.current_task().cancelled(): raise asyncio.CancelledError except asyncio.CancelledError: print(“Task was cancelled”) async def main(): task = asyncio.create_task(long_running_task()) await asyncio.sleep(5) # Let the task run for 5 seconds task.cancel() # Cancel the task print(“cancelled”) asyncio.run(main()) task.cancel() never gets called because it is single threaded and long_running_task() […]