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, Peter Ludemann, benjamin.peterson, fireattack, georg.brandl, gregory.p.smith, lisroach, lukasz.langa, miss-islington, pablogsal, thatch
Date 2020-12-06.12:01:27
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I don't see the point of augmenting the ast.parse, since we already have variants of proper CST implementations outside the core python. Such as or LibCST. 

Also for basic refactorings, it is so easy to use tokens for the refactoring and AST for the analysis! Even the ast.unparse() can be partially used (like first finding the related segment of the code through AST analysis, building the corresponding variant, unparsing it, finding the region of related tokens in the source code and replacing them). There are also quite a few libraries for using tokenize in different purposes (or wrappers) such as or
Date User Action Args
2020-12-06 12:01:27BTaskayasetrecipients: + BTaskaya, georg.brandl, gregory.p.smith, benjamin.peterson, thatch, lukasz.langa, fireattack, lisroach, pablogsal, miss-islington, Peter Ludemann
2020-12-06 12:01:27BTaskayasetmessageid: <>
2020-12-06 12:01:27BTaskayalinkissue36541 messages
2020-12-06 12:01:27BTaskayacreate