I'm in the process of writing C code for the purposes of traversing AST
nodes in the AST optimization branch.
This seems to be an ideal case for code generation based on the ASDL
representation of the AST as we're currently doing for Python-ast.[ch].
I'm already considering this approach for some code I need to visit the
C AST representation. We could likely write a similar generator for the
PyObject representation of the AST, which might be useful for the
proposed "ast" module. This would ensure that both implementations of
the AST visitation code are always kept in step with the ASDL.
The only real problem I can foresee with this is that the code in
asdl_c.py is already getting pretty hairy. Adding to the mess is going
to make it worse still. Maybe this will serve as a good opportunity to
clean it up a little? Any objections?
Cheers,
T
Paul Moore wrote:
2008/5/1 Georg Brandl <[EMAIL PROTECTED]>:
Armin Ronacher schrieb:
I would like to propose a new module for the stdlib for Python 2.6
and higher: "ast".
If there are no further objections, I'll add this to PEP 361 so that the
proposal doesn't get lost.
Excuse my confusion over process, but if this is to go into 2.6, does
that mean it needs to be ready before the first beta? Or is there a
more relaxed schedule for the stdlib (and if so, what is the deadline
for the stdlib)?
The same question probably applies to the stdlib reorg...
Paul.
_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/tom%40vector-seven.com
_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
