title: how to guarantee no py file can be compiled from my custom python interpreter?
body: <p>I'm trying to obfuscate my python code by editing the bytecodes of python in the .c files. something like the idea in this link:
  <a href="http://blog.quarkslab.com/building-an-obfuscated-python-interpreter-we-need-more-opcodes.html" rel="nofollow">a link</a>link
  <a href="http://www.expobrain.net/2013/09/04/simple-hardening-of-the-python-interpreter/" rel="nofollow">another helpful link</a></p>
  
  <p>I know that pyretic (<a href="https://github.com/MyNameIsMeerkat/pyREtic" rel="nofollow">https://github.com/MyNameIsMeerkat/pyREtic</a>) can reverse engineer this approach using the dis module. It compares the resulting dis of a scrambled opcode with resulting dis of a normal opcode.</p>
  
  <p>Of course an attacker can load the dis.py and our custom compiler will compile it to dis.pyc. So, any compiling build-in functionality has to be removed. Like compile_py, and compileall .. etc. how to guarantee they are all removed?</p>