[issue33349] 2to3 fails to parse async generators in non-async functions

Łukasz Langa added the comment: Thanks, Zsolt! ✨  ✨ -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue33349] 2to3 fails to parse async generators in non-async functions

Change by miss-islington : -- nosy: +miss-islington nosy_count: 4.0 -> 5.0 pull_requests: +26189 pull_request: https://github.com/python/cpython/pull/27702 ___ Python tracker

[issue33349] 2to3 fails to parse async generators in non-async functions

Change by miss-islington : -- pull_requests: +26190 pull_request: https://github.com/python/cpython/pull/27703 ___ Python tracker ___

[issue33349] 2to3 fails to parse async generators in non-async functions

Change by Łukasz Langa : -- versions: +Python 3.10, Python 3.11, Python 3.9 -Python 3.7, Python 3.8 ___ Python tracker ___ ___

[issue33349] 2to3 fails to parse async generators in non-async functions

Change by Zsolt Dollenstein : -- keywords: +patch pull_requests: +6288 stage: -> patch review ___ Python tracker ___

[issue33349] 2to3 fails to parse async generators in non-async functions

Change by Serhiy Storchaka : -- nosy: +benjamin.peterson, lukasz.langa, yselivanov ___ Python tracker ___

[issue33349] 2to3 fails to parse async generators in non-async functions

New submission from Zsolt Dollenstein : This is valid since python3.7: ``` def f(): return (i * 2 async for i in arange(42)) ``` but lib2to3 doesn't parse this properly, because `async` is tokenized as a `NAME` instead of `ASYNC` -- components: 2to3 (2.x to