[issue41879] Outdated description of async iterables in documentation of async for statement

Nick Gaya added the comment: As described above, the issue is in the textual description, not the code snippet. I have opened a GitHub PR with a fix. -- resolution: out of date -> status: closed -> open ___ Python tracker

[issue41879] Outdated description of async iterables in documentation of async for statement

Change by Nick Gaya : -- pull_requests: +22427 pull_request: https://github.com/python/cpython/pull/23548 ___ Python tracker <https://bugs.python.org/issue41

[issue39027] run_coroutine_threadsafe uses wrong TimeoutError

Nick Gaya added the comment: @msg358296: > IMO, it seems rather counter-intuitive to have to specify > `concurrent.futures.TimeoutError` when using a timeout for the future > returned by `run_coroutine_threadsafe()`. I think that's expected, given that the func

[issue41879] Outdated description of async iterables in documentation of async for statement

New submission from Nick Gaya : The documentation for the `async for` statement incorrectly states that "An asynchronous iterable is able to call asynchronous code in its iter implementation". Actually, this behavior was deprecated in Python 3.6 and removed in Python 3.7. As of