John Belmonte
John Belmonte
by the way, we track scheduling responsiveness like this: ```python3 # Latency of sleep(0) is used as a proxy for trio scheduler health. # A large latency implies that there...
I'm thinking about how this policy will affect API's. It's going to be common to have utility functions to compose awaitables. So e.g. an `wait_all()` would have to be: ```...
So if the wait functions have parameters, we need to resort to partial, correct? E.g. I have a ValueEvent which takes lambda etc. on wait. ``` await wait_all(partial(event.wait_value, lambda x:...
I'm seeing useful standard library functions which take raw coroutines: https://docs.python.org/3/library/contextlib.html#contextlib.AsyncExitStack
I tried the pylint work in progress but it's giving me a false positive at every use of await in my codebase. What am I missing?
now it's a WIP!
I've used patterns like this before of wrapping context managers-- it foils the proposed static checks. ```python @asynccontextmanager async def manager(some_args): ... yield ... def manager_wrap(): return manager(10) ```
in `manager_wrap()` the lint check will complain that `manager()` is called without await.
My take on the status for pylint: #700 is something I've had installed on my CI for a week now. The codebase happens to not have async generator functions. Handling...
It would also be nice to have a lint check for `async` functions not containing `await` or async control flow. Sometimes it can't be avoided (e.g. when implementing async methods...