Message5269

Kyle: thanks for the further analysis. CPython accepts arbitrary Python
objects pretty much anywhere in an ast.py tree, even if it fails at
parse time. Matching up with this behavior will require a complete
re-design (which I plan to do, but it's going to take a while). CPython
separates ast.py from the internal ast -- they are deliberately
different (ast.py is only a mirror of the internal ast so that it can
evolve). Not understanding this, I actually made Jython internal ast
implementation the same as ast.py. I plan to separate these in the
future (CPython design makes loads of sense *slaps forehead*)