[issue29205] col_offset for AsyncFunctionDef AST nodes is wrong

Change by Serhiy Storchaka : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue29205] col_offset for AsyncFunctionDef AST nodes is wrong

Serhiy Storchaka added the comment: Is this issue fixed? Are backports needed? I can't reproduce the issue on master and 3.7, but can reproduce it on 3.6. -- nosy: +benjamin.peterson, serhiy.storchaka versions: -Python 3.5, Python 3.7 ___ Python

[issue29205] col_offset for AsyncFunctionDef AST nodes is wrong

Change by Guo Ci Teo : -- pull_requests: +4144 stage: -> patch review ___ Python tracker ___

[issue29205] col_offset for AsyncFunctionDef AST nodes is wrong

Changes by Jelle Zijlstra : -- keywords: +patch Added file: http://bugs.python.org/file46215/issue29205.patch ___ Python tracker

[issue29205] col_offset for AsyncFunctionDef AST nodes is wrong

Jelle Zijlstra added the comment: The col_offset is actually correct when there is a decorator: In [26]: code = '@decorator\nasync def f(): pass' In [27]: tree = ast.parse(code) In [28]: tree.body[0].col_offset Out[28]: 0 The same issue appears with async for and async with: In [31]: code =

[issue29205] col_offset for AsyncFunctionDef AST nodes is wrong

New submission from Jelle Zijlstra: The col_offset attribute for ast.AsyncFunctionDef objects points to the "def" keyword, not to the "async" keyword that actually starts the node. Test case: In [18]: code = 'async def f(): pass' In [19]: tree = ast.parse(code) In [20]: tree.body[0]