Thomas Grainger

We should also help friends-of-dask enable `filterwarnings=error` so they are notified about these deprecations

> > This is a pattern that has been deprecated by CPython and our current implementation. > > I could be missing something, but I don't see the `loop=` keyword...

> Do you need more feedback or anything else to move on? No I don't think so, I'm mostly fixing places in the codebase and tests where a loop that's...

https://github.com/python/cpython/commit/903f0a02c16240dc769a08c30e8d072a4fb09154 Looks like Coroutines were deprecated but not Awaitables

on `python3.10 -W error` this passes: ```python class ExampleAwaitable: def __await__(self): async def _(): return await asyncio.sleep(0) return _().__await__() import asyncio print(f"{asyncio.iscoroutine(ExampleAwaitable())=}") async def amain(): await asyncio.wait([ExampleAwaitable()]) print("waited!") asyncio.run(amain()) ```...

I think we want to make most of these objects not Awaitables anyway eg. Nanny, Worker, ProcessInterface, MultiWorker where they can't really work correctly without `async with` `Future` is tricky...

see also https://github.com/dask/distributed/issues/4091

we missed a few tests that start the profiler by accident see #6498

@MichaelAquilina issue text updated

another option is to fallback to `python -m venv` where available