2012年1月11日 · .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 was a file format used before Python 3.5 for *.pyc files that were created with optimizations (-O) flag. (see the note below)

@Ankur: If there is a current *.pyc file, it will be executed. If not, the *.py file will be compiled, and then the compiled version will be executed. So if you already have a current *.pyc file, invoking the *.py file only takes a tiny bit longer - just how long it takes to compare two files' timestamps. –

2012年6月21日 · Every *.pyc file is a binary file containing next things: a four-byte magic number - it's simply bytes that change with each change to the marshalling code;

2015年7月13日 · To decompile compiled .pyc python3 files, I used uncompyle6 in my current Ubuntu OS as follows: Installation of uncompyle6: pip3 install uncompyle6 To create a .py file from .pyc file Run: uncompyle6 -o . your_filename.pyc Automatically a new .py file will be created with the same existing .pyc file name.

2016年7月31日 · In Python2 it compiles all .py files to .pyc files in a project which contains packages as well as modules. Whereas in Python3 it compiles all .py files to __pycache__ folders in a project which contains packages as well as modules. With browning from this post: You can enforce the same layout of .pyc files in the folders as in Python2 by using:

2011年3月1日 · A *.pyc file is created for imported modules, and they are placed in the same directory containing the .py file. However... no .pyc file is created for the main script for your program. In other words... if you call "python myscript.py" on the command line, there will be no .pyc file for myscript.py. This is how Python 2.x behaves.

2012年8月13日 · I have noticed .pyc files spontaneously being generated when some .py file of the same name gets run. What is the difference between .py and .pyc files? Also, I find that having .pyc files lying around clutters up space. Should one delete .pyc files? Or is there a benefit and/or necessity to having them around?

2019年9月19日 · A .pyc file is not an executable, it is Python bytecode meant to be ran by the Python interpreter. It compiles scripts to this before running them. It compiles scripts to this before running them. If you'd like to disassemble the Python bytecode, try the dis module.

2016年1月11日 · Super simple. Generating the .pyc file can done with the py_compile module found in the standard library. We simply pass in the name of the .py file and the name for our .pyc file in the following way: py_compile.compile('test.py', 'mypyc.pyc') This will place mypyc.pyc in our current working directory.

2011年5月23日 · The modification time of the version of spam.py used to create spam.pyc is recorded in spam.pyc, and the .pyc file is ignored if these don’t match. See the ref for more info. But some specific answers: The contents of the spam.pyc file are platform independent, so a Python module directory can be shared by machines of different architectures.