2 comments
Oooh it's a bytecode interpreter! I was wondering how they'd fit a parser/tokenizer in 500 lines unless the first was `import tokenizer, parser`. And it looks like 1500ish lines according to tokei<p>I think because python is a stack-based interpreter this is a really great way to get some exposure to how it works if you're not too familiar with C. A nice project!
See also <a href="https://github.com/nedbat/byterun" rel="nofollow">https://github.com/nedbat/byterun</a> and <a href="https://github.com/rocky/x-python" rel="nofollow">https://github.com/rocky/x-python</a>
And, in some ways, PyPy. I still think it is the sanest way to implement Python.<p>It makes me sad that I have to write C to make any meaningful changes to Python. Same goes for ruby. Rubinius was such a nice project.<p>Hacking on schemes and lisps made me realize how much more fun it is when the language is implemented in the language itself. It also makes sure you have the right abstractions for solving a bunch of real problems.