On Tue, Nov 19, 2019 at 10:24 PM Nathaniel Smith <njs@pobox.com> wrote:
On Mon, Nov 18, 2019 at 4:41 PM Pablo Galindo Salgado <pablogsal@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
* I have used the tool almost all the time I needed to deal with AST
* The public interface will have a very low surface API, keeping
part of the test suite. transformations. 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.
How does it compare to Berker's popular and well-maintained PyPI package for this? https://github.com/berkerpeksag/astor
Does that even have unparse() functionality? From the README it seems to focus on a nicer ast.dump(), which is quite different (in behavior and how it's used) from unparse(). -- --Guido van Rossum (python.org/~guido) *Pronouns: he/him **(why is my pronoun here?)* <http://feministing.com/2015/02/03/how-using-they-as-a-singular-pronoun-can-c...>