[issue44896] AttributeError in ast.unparse

Terry J. Reedy added the comment: #46073 may be a duplicate of this and perhaps should have the same resolution. -- nosy: +terry.reedy ___ Python tracker ___ _

[issue44896] AttributeError in ast.unparse

Change by Batuhan Taskaya : -- status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https:/

[issue44896] AttributeError in ast.unparse

Łukasz Langa added the comment: Sorry, I think we shouldn't be changing `ast.py` this way. To reiterate my review comment from the PR: I think we should just let this go and instead advertise that if you put new synthetic nodes in a tree, you have to either: - provide `lineno` and `col_offset

[issue44896] AttributeError in ast.unparse

Change by Łukasz Langa : -- versions: +Python 3.10, Python 3.11 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue44896] AttributeError in ast.unparse

Change by Batuhan Taskaya : -- keywords: +patch pull_requests: +26245 stage: -> patch review pull_request: https://github.com/python/cpython/pull/27770 ___ Python tracker ___

[issue44896] AttributeError in ast.unparse

Batuhan Taskaya added the comment: I don't think this is really an issue considering some other functionalities that consumes AST code (e.g `compile`) will expect it to be annotated with location metadata. This is why the `ast` module already comes bundled with a utility function called `fix

[issue44896] AttributeError in ast.unparse

Change by Terry J. Reedy : -- title: Issue with unparse in ast module -> AttributeError in ast.unparse ___ Python tracker ___ ___ Py