New ask Hacker News story: Ask HN: Ways to deal with Python 3.11 breaking change to asyncio

Ask HN: Ways to deal with Python 3.11 breaking change to asyncio
2 by m3047 | 0 comments on Hacker News.
AFAICT 3.11 requires your code to call asyncio.run(), whereas earlier versions (for some definition of "earlier") required you to inject your coroutines and then call loop.run_forever(). Basically it smells to me like this is going to require two distinct main()s. This is ugly. How do I make it not butt ugly and minimize the general odor?