On 11/23/05, Greg Ewing [EMAIL PROTECTED] wrote:
Brett Cannon wrote:
There are two problems to this topic; how to
get the AST structs into Python objects and how to allow Python code
to modify the AST before bytecode emission
I'm astounded to hear that the AST isn't made from
Python
I wrote (in the summary):
While there is no interface to the AST yet, one is
intended for the not-so-distant future.
Simon Burton wrote:
who is doing this ? I am mad keen to get this happening.
Brett Cannon wrote:
No one yet. Some ideas have been tossed around (read the thread for
On 11/22/05, Brett Cannon [EMAIL PROTECTED] wrote:
But if I had my way I think that having all AST objects be PyObjects
and then providing support for all three ways of getting access to the
AST (command-line, sys iterable, function for specific code object)
would be fantastic.
There needs
On 11/22/05, Neal Norwitz [EMAIL PROTECTED] wrote:
On 11/22/05, Brett Cannon [EMAIL PROTECTED] wrote:
But if I had my way I think that having all AST objects be PyObjects
and then providing support for all three ways of getting access to the
AST (command-line, sys iterable, function for
At 06:32 PM 11/22/2005 -0800, Brett Cannon wrote:
Hmm, it would be nice to give a function a module
name (like from an import statement) and have Python resolve it using
the normal sys.path iteration.
Yep, import path - filename path would be cool.
Zipped and frozen modules don't have
