Thomas Grainger

Are these the same issue? https://github.com/python/cpython/issues/115787 https://github.com/python/cpython/issues/105288

We probably need to use new_event_loop or asyncio.Runner here

Probably the simplest fix is to try get_event_loop, catch the RuntimeError and fall back to new_event_loop

> Hi @graingert, I left one suggestion. > > I noticed that the `asyncio.create_task()` calls in `handles/asgi.py` can benefit from this change as well (there are probably more places too)....

the problem is finalize_remaining does not issue a warning. A warning should be issued somewhere here: https://github.com/python-trio/trio/blob/c7801ae13052ed0aa65f7f6870476f20b0955d94/src/trio/_core/_asyncgens.py#L191-L193 but what to do if there's an exception?

I have a PR that fixes the deprecation warnings: https://github.com/catkin/catkin_tools/pull/767

> But it lacks the single call to entry_points for now. It uses functools.lru_cache to do a single call

I'm currently trying to work out if this change makes it possible to test https://github.com/python-trio/trio/blob/12e8395cf6939ec9f00df122487dc66ef774fec8/src/trio/_core/_run.py#L2790

I think it's best to wait for this PR: https://github.com/encode/uvicorn/pull/2435 which will then work with `--loop=winloop:new_event_loop`

Probably we need to switch to use trustme instead of hard coded certs