On 16/09/20 9:34 am, Pablo Galindo Salgado wrote:
The first is that deleting a deep tree currently is just freeing the arena block, while if the nodes were PyObjects it will involve recursive destruction. That could potentially segfault
Not sure why that would be a concern. It's theoretically a possibility with any Python data, but we don't seem to worry about it. Why should it be a problem in the compiler specifically?
* The proposal seems to imply that the AST will be a fully public and stable API.
We already have two kinds of AST, the one used internally by the compiler, and the one exposed to Python in the ast module. The only time the latter should need to change is if there is a change in the syntax of the language, so why not promise to keep it stable and use it as the form taken and produced by the macro processors? -- Greg _______________________________________________ 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/7KO7GJ7RTWPZ4BX6EESDE6TC6TBVLMJ3/ Code of Conduct: http://python.org/psf/codeofconduct/
