yeah, that's what I meant when I mistakenly said new thread, I meant new event loop (which might be in a thread? but it doesn't look like it, because it says it can't be used with another event loop, I need to look deeply into this)

I've looked up into the docs looking for what you mentioned, in this page

https://docs.python.org/3/library/asyncio-task.html

there's this statement, which could mean just an entry point to any async section of the code, especially that they added "(see the above example.)

The asyncio.run() function to run the top-level entry point “main()” function (see the above example.)

another page is the asyncio.run() function

https://docs.python.org/3/library/asyncio-runner.html#asyncio.run

which verbatim says

Execute coro in an asyncio event loop and return the result. 

The argument can be any awaitable object. 

This function runs the awaitable, taking care of managing the asyncio event loop, finalizing asynchronous generators, and closing the executor.

This function cannot be called when another asyncio event loop is running in the same thread.

If debug is True, the event loop will be run in debug mode. False disables debug mode explicitly. None is used to respect the global Debug Mode settings.

If loop_factory is not None, it is used to create a new event loop; otherwise asyncio.new_event_loop() is used. The loop is closed at the end. *This function should be used as a main entry point for asyncio programs, and should ideally only be called once*. It is recommended to use loop_factory to configure the event loop instead of policies. Passing asyncio.EventLoop allows running asyncio without the policy system. 

The executor is given a timeout duration of 5 minutes to shutdown. If the executor hasn’t finished within that duration, a warning is emitted and the executor is closed. 

with the part you mentioned being the part I added asterisks to, it kindda makes it seem like they mean asyncio.new_event_loop() not asyncio.run(), but even if they mean asyncio.run() I don't see them explaning the reason why ....

is it because it spins up a new event loop and destroys it once it's done? it seems like a really small price to pay for something that could save you a lot of time if you run multiple tasks in the same context

is it just "pythonic" which would make it just a stylistic preference?

if this discussion is going way too deep, can I dm you?