Just wanted to add my +1 to this idea. Moving it to ast module will add little maintenance costs, but will make it easier to use.
-- Ivan On Tue, 19 Nov 2019 at 00:46, Pablo Galindo Salgado <pablog...@gmail.com> wrote: > 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-le...@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/JAQDBMC23HW2PQ27HQNJ7G244T423IDD/ > Code of Conduct: http://python.org/psf/codeofconduct/ >
_______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@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/GKFY5NBBD5VL5EODKMH7D2TFNB7RWZEJ/ Code of Conduct: http://python.org/psf/codeofconduct/
