which parser to use

Jean Brouwers mrjean1ATcomcastDOTnet at no.spam.net
Tue Feb 22 03:45:17 EST 2005


Check out SimpleParse/mxTextTools.  Just an outstanding E/BNF driven
parser, very highly recommended.

 <http://simpleparse.sourceforge.net/>

/Jean Brouwers

PS) See also

<http://www-128.ibm.com/developerworks/linux/library/l-simple.html>

<http://gnosis.cx/publish/programming/charming_python_b4.html>

There are descriptions of other Python-based parsers on this site
<http://gnosis.cx/TPiP/>



In article <87ll9hmdd6.fsf at subopt.house-net>, <a_nuther at geek.org> wrote:

> I'm building something that requires parsing a rather complex
> language. I'd like to do the whole application, including the
> lex/parse phase, in Python (for development/debug speed), and only
> move parts of it to a compiled language if execution speed absolutely
> dictates. So, what i'm looking for in a Python parser is:
> 
>     1) reliability (don't want to debug a parser)
>     1) flexibility (i do a lot of refactoring)
>     2) E/BNF friendliness (working from a spec)
>     3) speed (moderate speed will do; glacial won't)
> 
> Does anyone have any familiarity with some of the several Python
> parsers out there? Any pointers to comparisons (as opposed to surveys)
> of _several_ of the Python parsers would be much appereciated. (I've
> seen the YAPPS/Spark comparison.) If none of the Python parsers really
> fit the bill, any thoughts on ANTLR, Spirit, etc?
> 
> Thanks in advance,
> E
>



More information about the Python-list mailing list