RetroSearch Browse

Sat Sep 23 16:59:14 CEST 2006 · https://mail.python.org/pipermail/python-dev/2006-September/068978.html

Anthony Baxter <anthony at interlink.com.au> writes:

> I'd like to propose that the AST format returned by passing PyCF_ONLY_AST 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

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2006-September/068978.html below:

[Python-Dev] AST structure and maintenance branches