There's a fairly extensive discussion here: https://github.com/python/asyncio/pull/465

In short, asyncio.run() is a pretty straightforward addition, so let's add it.

The discussion was more focused on the asyncio.run_forever() proposal.  I now think that it shouldn't be implemented in asyncio.  Instead we should fix cases where 'loop.run_forever' is usually required.  Mainly that's servers, and they are easily fixable by making "Server" an async context manager and implementing a "server.serve_forever()" method.  That way, with asyncio.run():

    async def serve_something():
       async with asyncio.start_server(...) as server:
           await server.serve_forever()

    asyncio.run(serve_something())  # No loop.run_forever()!

I like avoiding run_forever() -- the function always was too cumbersome.

I'll open a separate issue to improve Server's API.  AFAIK it's the main reason for having run_forever().

New changeset 02a0a19206da6902c3855a1fa09e60b208474cfa by Yury Selivanov in branch 'master':
bpo-32314: Implement asyncio.run() (#4852)
https://github.com/python/cpython/commit/02a0a19206da6902c3855a1fa09e60b208474cfa

Wow, I really love your new function. Thanks Yury! asyncio examples in the doc look much better now!

> Wow, I really love your new function. Thanks Yury! asyncio examples in the doc look much better now!

This year I'll stay for the sprints at PyCon, and will focus on improving the docs further.  I needed asyncio.run for that :)

New changeset a4afcdfa55ddffa4b9ae3b0cf101628c7bff4102 by Yury Selivanov in branch 'master':
bpo-32314: Fix asyncio.run() to cancel runinng tasks on shutdown (#5262)
https://github.com/python/cpython/commit/a4afcdfa55ddffa4b9ae3b0cf101628c7bff4102