[pypy-dev] parser compiler and _ast

Antonio Cuni anto.cuni at gmail.com
Mon Jan 26 14:24:14 CET 2009

Maciej Fijalkowski wrote:
> I did a bit of research on a matter of different python interfaces to
> parsing. This is a bit of a mess, but it is as follows:
> 1a. We just always generate the code and throw it away. We loose
> performance, but we don't care
> (and we pass tests)

a quick google code search reveals that there are a couple of projects using 
parser, like pychecker, epydoc and quixote. If it's not too time consuming, I 
would go for this option.

> 2. We slowly deprecate parser & compiler, with some removal in future


> 3. If we develop a new parser, we drop compatibility with exact
> concrete syntax trees and
> we only keep ast around (as ast module) if people want to interact
> with it (this is one less
> worry for writing parser).

That's an option, but not for 1.1, I think.


More information about the Pypy-dev mailing list