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 Python 3.7, the `__aiter__()` method must return an asynchronous iterator directly.

Suggested fix: Update the `async for` statement description for Python 3.7+ to match the "Asynchronous Iterators" section in the data model documentation.

> An :term:`asynchronous iterator` can call asynchronous code in its *next* method.

Relevant documentation:
- https://docs.python.org/3/reference/compound_stmts.html#the-async-for-statement
- https://docs.python.org/3/reference/datamodel.html#asynchronous-iterators

Both mentioned links have the correct code.
They use sync __aiter__ and async __anext__

As described above, the issue is in the textual description, not the code snippet. I have opened a GitHub PR with a fix.

You are right.

New changeset 4b8cdfcb22fbeaab9d954cb693a7fb3362a382b6 by Nick Gaya in branch 'master':
bpo-41879: Doc: Fix description of async for statement (GH-23548)
https://github.com/python/cpython/commit/4b8cdfcb22fbeaab9d954cb693a7fb3362a382b6

New changeset be9e4402db64564f7bf0fedb3769cead46c0d4c4 by Miss Islington (bot) in branch '3.9':
[3.9] bpo-41879: Doc: Fix description of async for statement (GH-23548) (GH-23749)
https://github.com/python/cpython/commit/be9e4402db64564f7bf0fedb3769cead46c0d4c4