[Python-Dev] AST structure and maintenance branches (original) (raw)
Michael Hudson mwh at python.net
Sat Sep 23 16:59:14 CEST 2006
- Previous message: [Python-Dev] AST structure and maintenance branches
- Next message: [Python-Dev] AST structure and maintenance branches
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Anthony Baxter <anthony at interlink.com.au> writes:
I'd like to propose that the AST format returned by passing PyCFONLYAST to compile() get the same guarantee in maintenance branches as the bytecode format - that is, unless it's absolutely necessary, we'll keep it the same. Otherwise anyone trying to write tools to manipulate the AST is in for a massive world of hurt.
Anyone have any problems with this, or can it be added to PEP 6?
Sounds like a good idea.
Cheers, mwh
-- Reading Slashdot can [...] often be worse than useless, especially to young and budding programmers: it can give you exactly the wrong idea about the technical issues it raises. -- http://www.cs.washington.edu/homes/klee/misc/slashdot.html#reasons
- Previous message: [Python-Dev] AST structure and maintenance branches
- Next message: [Python-Dev] AST structure and maintenance branches
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]