This was useful for me to make a restricted environment
by disallowing specific opcodes.

Logged In: YES 
user_id=21627

Can you please elaborate? In what way does is that useful
for a restricted environment?

Logged In: YES 
user_id=31435

I'm also missing the connection to restricted environments.

If you want to capture dis output (or output from anything else 
that uses print), the usual way to do it is to assign a StringIO 
instance (or other file-like object) to sys.stdout before 
invoking dis.

Logged In: YES 
user_id=55188

Yes. To disallow BINARY_POWER and INPLACE_POWER, I'm hooking
sys.stdout now. But, because it isn't thread-safe way, I
needed to lock threads whenever I print something to stdout.
To make a cheaper solution, I like this patch.

Logged In: YES 
user_id=21627

So you want to find out whether BINARY_POWER is in the byte
code? If so, I suggest that usage of dis.disassemble is
inadequate. Instead, you should just copy the essential part
of the disassemble loop, and look for an opcode for which
dis.opname[opcode] is 'BINARY_POWER'. This will be much
faster, and thread-safe.

Logged In: YES 
user_id=55188

Ah. Thank you for your comments. It looks much better than
parsing dis's output.