> AFAIK the AST is > CPython-specific so should be treated with the same attitude as > changes to the bytecode. That means, do it conservatively, since there > *are* people who like to write tools that manipulate or analyze this, > and while they know they're doing something CPython and > version-specific, they should not be broken by bugfix releases, since > the people who *use* their code probably have no idea of the deep > magic they're depending on. PyPy implements exactly the same AST. I think Jython also does, although I'm not that sure. There were already issues with say subclassing ast nodes were pypy was incompatible from CPython. That said, it's completely fine from PyPy's perspective to change AST between major releases.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4