pyc

Is there a way to change the directory where .pyc file are created by the Python interpreter? I saw two PEPs about that subject ( 0304 and 3147 ), but none seems to be implemented in the default interpreter (I'm working with Python 3). Did I miss something ? There's no way to change where the .pyc files go. Python 3.2 implements the __pycache__ scheme whereby all the .pyc files go into a directory named __pycache__ . Python 3.2 alpha 1 is available now if you really need to keep your directories clean. Until 3.2 is released, configure as many tools as you can to ignore the .pyc files. Hans

I have a .pyc file. I need to understand the content of that file to know how the disassembler works of python, i.e. how can I generate a output like dis.dis(function) from .pyc file content. for e.g. >>> def sqr(x): ... return x*x ... >>> import dis >>> dis.dis(sqr) 2 0 LOAD_FAST 0 (x) 3 LOAD_FAST 0 (x) 6 BINARY_MULTIPLY 7 RETURN_VALUE I need to get a output like this using the .pyc file. Martijn Pieters .pyc files contain some metadata and a marshal ed code object; to load the code object and disassemble that use: import dis, marshal, sys # Header size changed in 3.3. It might change again,

I understand that ".pyc" files are compiled versions of the plain-text ".py" files, created at runtime to make programs run faster. However I have observed a few things: Upon modification of "py" files, program behavior changes. This indicates that the "py" files are compiled or at least go though some sort of hashing process or compare time stamps in order to tell whether or not they should be re-compiled. Upon deleting all ".pyc" files ( rm *.pyc ) sometimes program behavior will change. Which would indicate that they are not being compiled on update of ".py"s. Questions: How do they decide

What do these python file extensions mean? .pyc .pyd .pyo What are the differences between them and how are they generated from a *.py file? Bill Lynch .py : This is normally the input source code that you've written. .pyc : This is the compiled bytecode. If you import a module, python will build a *.pyc file that contains the bytecode to make importing it again later easier (and faster). .pyo : This is a *.pyc file that was created while optimizations ( -O ) was on. .pyd : This is basically a windows dll file. http://docs.python.org/faq/windows.html#is-a-pyd-file-the-same-as-a-dll Also for