For all I know Chris' intent he does want to make it work.
Last time around though part of the problem was Google not allowing ast.py
and workarounds had to be sought. Not sure what the status is on that.
--
Jeroen Ruigrok van der Werven <asmodai(-at-)in-nomine.org> / asmodai
イェルーン ラウフロック ヴァン デル ウェルヴェン
http://www.in-nomine.org/ | http://www.rangaku.org/ | GPG: 2EAC625B
Teaching should be such that what is offered is perceived as a valuable
gift and not as a hard duty...
Definitely.
However I'm not sure the approach used on the branch is the right one.
Google is likely to enable the _ast module in the future, and in the
meantime, a dirty but working hack is available to make use of _ast on
App Engine.
The long term fix for App Engine support would be to switch to Python
code generation instead of AST transformation, and use _ast to get the
AST as the basis for the code generation, falling back to the compiler
package on Python 2.4.
In the short term, it should be relatively easy to complete that
branch by implementing the py:with and py:for directives in an AST-
less manner. That's really all that's missing right now. But that
branch is very unlikely to be merged back into the mainline, as I'd
rather go the codegen+_ast route described above.
Cheers,
--
Christopher Lenz
cmlenz at gmx.de
http://www.cmlenz.net/