Comments on: Exploring Python Bytecode

By: Python Links : Well, at least we got the duck.

Python Links : Well, at least we got the duck. — Tue, 22 Sep 2009 11:21:21 +0000

[...] ORM Mapper – http://www.sqlalchemy.org/ Python ByteCode – http://thermalnoise.wordpress.com/2007/12/30/exploring-python-bytecode/ Performance – [...]

By: Ananth

Ananth — Sat, 13 Jun 2009 15:35:33 +0000

Alex Martelli’s Talk: http://www.youtube.com/watch?v=23s9Wc3aWGY

Covers some bytecode towards the end. Not a lot of information – but still useful.

Plus Py3K has a new peephole.c with mildly interesting optimizations. But the best progress here has been through unladen swallow – http://code.google.com/p/unladen-swallow/. They have a LLVM codegen working.

I might do a more up2date “state of the python runtime” post soon.

By: jason fager - Language-level Support for Software Configuration

jason fager - Language-level Support for Software Configuration — Mon, 30 Mar 2009 06:50:36 +0000

[...] idea, it’s just a nudge in that direction, to see what’s possible. Thanks are due to Thermal Noise for getting me pointed in the “right” direction for the bytecode stuff. [...]

By: zeo

zeo — Thu, 12 Jun 2008 09:33:54 +0000

god damned !!!!
is there a website where i can figure out how to use byteplay ?
there seems to be no real documentation about byteplay,
not any instructions on how to use it on the web!!

i want to “disassemble” a .pyc file, modify and “reassemble” it
could anybody explain this step by step for a non python supergeek
is byteplay the best way to to this anyway?

(sorry for swaring!) zeo

By: Jeffrey

Jeffrey — Tue, 06 May 2008 10:06:40 +0000

I think it was a great idea to peep into the pyc file.
Good work !

jeff

By: Jeremy

Jeremy — Sat, 12 Jan 2008 01:42:43 +0000

I’m sure you know this, but the optimizations you’re talking about are not peephole optimizations. In typical compilers, these optimizations are handled on the DAGs, i.e. before code generation or peephole optimization. Peephole optimization typically refers to the last stage in optimization that just removes instructions that make little sense.

By: Pages tagged "python"

Pages tagged "python" — Tue, 08 Jan 2008 18:36:14 +0000

[...] online community. The best part is … it’s all 100% free! Check them out here: Join Hey Nielsen! Exploring Python Bytecode « Thermal Noise saved by 1 others Gaararox125 bookmarked on 01/08/08 | [...]

By: Ananth

Ananth — Wed, 02 Jan 2008 07:36:24 +0000

Hey Guys,

I did know about the dis module. See Line 20 in the source
However I don’t like two things about it.

1. It just prints the instruction sequence on stdout. I would rather have it as a list of tuples that I can process programatically – detect instruction sequences for example.

2. It prints out blocks of instructions corresponding to source lines. I would rather prefer to group instruction sequences corresponding to Basic Blocks. I have an augmented pretty_print version that does this.

Anyway these are just some random notes from my study. The disassemble function was for my own understanding – not a replacement for the dis() module.

By: Björn Schließmann

Björn Schließmann — Wed, 02 Jan 2008 00:37:39 +0000

To complement Phillip’s posting: Instead of using this huge decompile function, try:

def foo_simple():
[...]

import dis
dis.dis(foo_simple)

By: Phillip J. Eby

Phillip J. Eby — Mon, 31 Dec 2007 22:47:53 +0000

The stdlib includes a disassembler: http://python.org/doc/2.5/lib/module-dis.html

And PyPI lists my assembler: http://pypi.python.org/pypi/BytecodeAssembler