I don't understand what problem this is a practical solution to. This thread started with MAL's questions about finding errors in Python code. You mentioned an effort to write a lint-like tool. It may be that YACC has great support for error recovery, in which case MAL might want to look at for his tool.
But in general, the most practical solution for parsing Python is probably to use the Python parser and the builtin parser module. It already exists and seems to work just fine.
Probably not that relevant any more, but MAL originally asked for a parser that doesn't stop at the first error. That's a real weakness of the existing parser!!!
--Guido van Rossum (home page: http://www.pythonlabs.com/%7Eguido/)