In a previous thread I said that work on this project is complete. However, I have some news to report.
Guido and I have been discussing whether it makes sense to add the capabilities of leoAst.py to python's stdlib. We both now agree that doing so would be a bad idea. To summarize: adding even the simplest new function to python's ast module would imply exposing the api's of the TokenOrderGenerator and TokenOrderTraverser classes. Alas, doing so would cast those api's in stone forever. It's not something for which I want to be responsible. There is some disappointment in the conclusion. Happily, there is a big consolation prize. Guido is open to adding links to leoAst.py at the bottom of the docs for the ast module <https://docs.python.org/3/library/ast.html>. Such a link would be a big deal. The link would amount to be a strong endorsement of leoAst.py. To mute possible pushback against adding these links, I'll be coordinating discussions with the devs for asttokens <https://pypi.org/project/asttokens/>, parso <https://github.com/davidhalter/parso>and LibCST <https://github.com/Instagram/LibCST>, with the aim of adding links to these tools as well. All in all, this seems like the best possible result for leoAst.py. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/f0cbfc48-b533-4ea1-8e90-1223581c21d0o%40googlegroups.com.
