This is a really great idea, after pretty ast.dump it will be great
addition for people who works with AST code transformations.
I think with the new end_lineno and end_col_offset information output can
be little bit close the original.
I want to volunteer the work if there is an open opportunity after
consensus about adding this.
On Tue, Nov 19, 2019, 3:45 AM Pablo Galindo Salgado
Hi,
What do people feel about exposing Tools/parser/unparse.py in the standard library? Here is my initial rationale:
* The tool already needs to be maintained and updated as is tested as part of the test suite. * I have used the tool almost all the time I needed to deal with AST transformations. * The public interface will have a very low surface API, keeping maintaining it (the public interface) a very small burden IMHO.
We could add the public interface to the ast.py module or a new one if people feel strongly about it.
Does anyone feel strongly against this or have any objection that I am not contemplating?
Regards from rainy London, Pablo Galindo Salgado _______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-leave@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/JAQDBMC2... Code of Conduct: http://python.org/psf/codeofconduct/