A Python Interpreter Written in Python

(aosabook.org)

54 points | by xk3 3 days ago

7 comments

  • blueybingo 13 minutes ago
    the article glosses over something worth pausing on: the `getattr` trick for dispatching instructions (replacing the big if-elif chain) is actaully a really elegant pattern that shows up in a lot of real interpreters and command dispatchers, not just toy ones -- worth studying that bit specifically if you're building anything with extensible command sets.
  • anitil 2 hours ago
    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

    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!

  • andltsemi3 7 minutes ago
    "Yaw dog I heard you liked python, so I put python in your python so you can interpret python while you interpret python"
  • tekknolagi 3 hours ago
    • bjoli 2 hours ago
      And, in some ways, PyPy. I still think it is the sanest way to implement Python.

      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.

      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.

      • anitil 2 hours ago
        > And, in some ways, PyPy

        What do you mean by that? I'm not familiar with PyPy

        • nxpnsv 2 hours ago
          PyPy is python implemented in python. It is fast.
  • woadwarrior01 1 hour ago
    aka A Metacircular Interpreter
  • kevinten10 28 minutes ago
    [dead]
  • hcfman 2 hours ago
    Just wondering why you stopped there? Why not a python interpreter for a python interpreter for python ?