This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author BTaskaya
Recipients BTaskaya, pablogsal, thautwarm
Date 2019-12-01.18:50:20
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1575226220.65.0.51980803457.issue35632@roundup.psfhosted.org>
In-reply-to
Content
Tools/parser/unparse.py has been moved under ast module and exposed via ast.unparse() interface. If you want to support custom AST statements, the current version is incapable of doing such changes because of the real unparser class is private. As a workaround you can import it and subclass it /assign a method and then use ast.unparse() but that is a hacky way and there is no one who can guarantee if that unparser class will change its API or not. Currently it uses NodeVisitor API. Also you can use Berker's astor project to do this job, which gives you ability of changing source generator class.
History
Date User Action Args
2019-12-01 18:50:20BTaskayasetrecipients: + BTaskaya, pablogsal, thautwarm
2019-12-01 18:50:20BTaskayasetmessageid: <1575226220.65.0.51980803457.issue35632@roundup.psfhosted.org>
2019-12-01 18:50:20BTaskayalinkissue35632 messages
2019-12-01 18:50:20BTaskayacreate