https://github.com/albertz/PyCParser

A C parser and interpreter written in Python. Also includes an automatic ctypes interface generator.

It is looser than the C grammar, i.e. it should support a superset of the C language in general.

Some of the support may a bit incomplete or wrong at this point because I didn't really strictly followed the language specs but rather improved the parser by iteration on real-world source code.

Parsers / ctypes interface generators:

• pyclibrary (Github fork). Is quite slow and didn't worked that well for me.
• The equally named pycparser. It depends on Python Lex-Yacc. (I didn't really tested it yet.)
• pycparser. Another complete C99 parse in pure Python. (I didn't tested it yet. Seems to make good progress.)
• ctypesgen. Also uses Lex+Yacc.
• codegen. Uses GCC-XML. See below about the disadvantages of such an aproach.

Interpreters:

There aren't any in Python. So I list all I know about.

• CINT. Probably the most famous one.
• Ch. Is not really free.
• ups debugger.
• PicoC. "A very small C interpreter."

• Be more flexible. It is much easier now with a hand-written parser to do operations on certain levels of the parsing pipe.
• I wanted to have some self-contained code which can also easily run on the end-user side. So the end-user can just update the lib and its headers and then some application using this Python lib will automatically use the updated lib. This is not possible if you generated the ctypes interface statically (via some GCC-XML based tool or so).
• I wanted to implement PySDL and didn't wanted to translate the SDL headers by hand. Also, I didn't wanted to use existing tools to do this to avoid further maintaining work at some later time. See the project for further info.
• This functionality could be used similarly for many other C libraries.
• A challenge for myself. Just for fun. :)

• PySDL. Also uses the automatic ctypes wrapper and maps it to a Python module.
• PyCPython. Interpret CPython in Python.
• PyLua. Interpret Lua in Python.

Also see the tests/test_interpreter.{c,py} 'Hello world' example.

• I'm quite sure that function pointer typedefs are handled incorrectly. E.g. typedef void f(); and typedef void (*f)(); are just the same right now. See cpre3_parse_typedef and do some testing if you want to fix this.
• Array initializers (e.g. {1,2,3}) aren't correctly handled by the interpreter.
• gotos are not handled by the interpreter.
• Function pointers don't work quite correct in the interpreter.
• Many functions from the standard C library are still missing.
• There might be some bugs. :)
• C++ isn't supported yet. :)

--- Albert Zeyer, http://www.az2000.de