I have the following code:

Given this simple snippet, why does the first anext() call work
but the second anext() results in a strange error?

I need to have several functions running concurrently and infinitely. I plan to use asyncio for this, and, if possible, I want to avoid using event loop directly.

I need to have several functions running concurrently and infinitely. I plan to use asyncio for this, and, if possible, I want to avoid using event loop directly.

I need to have several functions running concurrently and infinitely. I plan to use asyncio for this, and, if possible, I want to avoid using event loop directly.

I need to have several functions running concurrently and infinitely. I plan to use asyncio for this, and, if possible, I want to avoid using event loop directly.

I need to have several functions running concurrently and infinitely. I plan to use asyncio for this, and, if possible, I want to avoid using event loop directly.

I have two tasks, I want to run them with asyncio concurrently (not in a thread).
But if the tasks are a common function, they will be run one by one. I’m having a hard time making the function async.

As I understand it : if an asyncio task is waiting on a future and this future is destroyed by the garbage collector then the task is destroyed too. Which is great because the task would never have completed anyway because the future will never have a result.
This behavior makes total sense, I might have in my program futures that are destroyed and I like that the tasks that could be waiting on them will not cause memory leak by sticking around. How can I get read of the warning message “Task was destroyed but it is pending!” that is printed in the console each time this happens ?

I need to have several functions running concurrently and infinitely. I plan to use asyncio for this, and, if possible, I want to avoid using event loop directly.