No, sadly there’s no way to get a .py file using Papaya, since it is just a disassembler, not a decompiler.

What papaya outputs is a representation of the actual bytecodes of the Python virtual machine.

In theory it would be possible to generate a .py file from a .pyc file, but I don’t think I want to be the one to try it.

@Thomas: I do know about using for .. in, and that was what I was using originally, in fact. The reason that I switched it to the ugly way it is written now is because the encode_op method will pass the input generator into a recursive call of the asm method…and I thought that it wouldn’t work to do it the pretty way.

Of course, I just checked and you can, in fact have nested for loops on the same generator and it will work the same way. Well, that will look much better after fixing that, thanks!

In the main assembler loop:

while True: try: op = input.next() except StopIteration: break # …

can be replaced with this:

for op in input: # …

(I tried to send you a small patch regarding this, but it seems my local SMTP server needs some more configuration before it will play nice with git-send-email)

This is a somewhat more “Pythonic” way to deal with your input. You can use “for” with any sequence or generator. Generators are especially funky. I’ve found them frequently useful. I’m actually writing up a post on how the Python compiler constructs generator functions: syntactically they look just like functions, but under the hood there’s a bit of voodoo going on

Plus, with PPya, I could also make it a recursive acronym along the lines of “PPya: Python assembler.”

Wait, I’ve got it, PPya now stands for “Papaya Python assembler.”

It’s not a recursive acronym, it’s an acronym with a sound-alike first word.