Andrew Godwin

This bug looks very like #392 - are you sure that coverage is not running in a separate virtualenv or similar with an old typing_extensions package?

Hmm, this is perplexing. It's possible it's `pypy` instead - are you able to try on cpython?

OK, so this must be some sort of pypy typing incompatability. Have you tried pypy3.9? I'm not sure if we have a sensible way to fix this other than saying...

I suspect we'll just have to say that pypy is incompatible with the typing in asgiref 3.7 for now then, which is annoying. I'll investigate and see if we can...

Actually, it's normal for multiple executors to be created. The specific behaviour should be: * If the call is marked as `thread-sensitive`, there's a single shared global executor that is...

Since all sorts of things that you can do in your app can affect that (different middleware, server configuration, loading in something that uses gevent, etc.), we can only really...