blocks|key|2914138|text|这通常是你已经编译过的输入源代码，这是编译后的字节码。，written.|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2914139|.pyc：，|unordered-list-item|offset|length|style|CODE|2914140|.py：，written.|ordered-list-item|2914141|.pyc：。如果您导入一个模块，python将构建一个包含字节码的*.pyc文件，以便于以后再次导入(+faster).|2914142|.pyo：这是Python3.5之前用于使用优化(-O)标志创建的*.pyc文件的一种文件格式。(参见注释below)|2914143|.pyd：这基本上是一个windows+dll文件。http://docs.python.org/faq/windows.html#is-a-pyd-file-the-same-as-a-dll|2914144|2914145|2914146|另外，有关.pyc与.pyo的进一步讨论，请查看：http://www.network-theory.co.uk/docs/pytut/CompiledPythonfiles.html+(我复制了下面的重要部分)|2914147|2914148|blockquote|2914149|2914150|2914151|使用-O标志调用Python解释器时，会生成优化代码并将其存储在‘.pyo’文件中。优化器目前帮助不大；它只删除断言语句。当使用-O时，所有字节码都被优化；.pyc文件被忽略，.py文件被编译为优化的Python解释器(-OO)的两个-O标志将导致字节码编译器执行在极少数情况下可能导致程序故障的优化。目前，只从字节码中删除__doc__字符串，从而生成更紧凑的“.pyo”文件。由于某些程序可能依赖于这些可用选项，因此只有在您知道自己在做什么的情况下才应该使用此选项。|2914152|程序从‘.pyc’或‘.pyo’文件读取时的运行速度不会比从‘.py’文件读取时快；‘.pyc’或‘.pyo’文件唯一快的是加载速度。|2914153|当通过在命令行上提供脚本名称来运行脚本时，脚本的字节码永远不会写入‘.pyc’或‘.pyo’文件。因此，通过将脚本的大部分代码移动到一个模块，并使用一个小的引导脚本来导入该模块，可以减少脚本的启动时间。也可以直接在命令行中命名‘.pyc’或‘.pyo’文件。|2914154|2914155|备注：|BOLD|2914156|2015年9月15日，Python+3.5+release实施了PEP488并删除了.pyo文件。这意味着.pyc文件同时表示未优化和优化的字节码。|2914157|entityMap|0|LINK|mutability|MUTABLE|url|http://docs.python.org/faq/windows.html#is-a-pyd-file-the-same-as-a-dll|1|https://web.archive.org/web/20160130165632/http://www.network-theory.co.uk/docs/pytut/CompiledPythonfiles.html|2|https://docs.python.org/3/whatsnew/3.5.html#pep-488-elimination-of-pyo-files^0|0|0|4|0|0|3|0|0|4|X|5|0|0|4|P|2|X|5|0|0|4|Q|1Z|0|0|0|0|5|4|A|4|P|1V|1|0|0|0|0|0|4I|7|0|0|0|0|0|3|0|16|4|1H|4|B|I|2|0^^$0|@$1|2|3|4|5|6|7|1O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|1P|8|@$E|1Q|F|1R|G|H]]|9|@]|A|$]]|$1|I|3|J|5|K|7|1S|8|@$E|1T|F|1U|G|H]]|9|@]|A|$]]|$1|L|3|M|5|K|7|1V|8|@$E|1W|F|1X|G|H]|$E|1Y|F|1Z|G|H]]|9|@]|A|$]]|$1|N|3|O|5|K|7|20|8|@$E|21|F|22|G|H]|$E|23|F|24|G|H]|$E|25|F|26|G|H]]|9|@]|A|$]]|$1|P|3|Q|5|K|7|27|8|@$E|28|F|29|G|H]]|9|@$E|2A|F|2B|1|2C]]|A|$]]|$1|R|3|-4|5|6|7|2D|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|2E|8|@]|9|@]|A|$]]|$1|T|3|U|5|6|7|2F|8|@$E|2G|F|2H|G|H]|$E|2I|F|2J|G|H]]|9|@$E|2K|F|2L|1|2M]]|A|$]]|$1|V|3|-4|5|6|7|2N|8|@]|9|@]|A|$]]|$1|W|3|-4|5|X|7|2O|8|@]|9|@]|A|$]]|$1|Y|3|-4|5|6|7|2P|8|@]|9|@]|A|$]]|$1|Z|3|-4|5|6|7|2Q|8|@]|9|@]|A|$]]|$1|10|3|11|5|D|7|2R|8|@$E|2S|F|2T|G|H]]|9|@]|A|$]]|$1|12|3|13|5|D|7|2U|8|@]|9|@]|A|$]]|$1|14|3|15|5|D|7|2V|8|@]|9|@]|A|$]]|$1|16|3|-4|5|6|7|2W|8|@]|9|@]|A|$]]|$1|17|3|18|5|6|7|2X|8|@$E|2Y|F|2Z|G|19]]|9|@]|A|$]]|$1|1A|3|1B|5|6|7|30|8|@$E|31|F|32|G|H]|$E|33|F|34|G|H]]|9|@$E|35|F|36|1|37]]|A|$]]|$1|1C|3|-4|5|6|7|38|8|@]|9|@]|A|$]]]|1D|$1E|$5|1F|1G|1H|A|$1I|1J]]|1K|$5|1F|1G|1H|A|$1I|1L]]|1M|$5|1F|1G|1H|A|$1I|1N]]]]

<ol>
<li><code>.py</code>: This is normally the input source code that you've written.</li>
<li><code>.pyc</code>: This is the compiled bytecode. If you import a module, python will build a <code>*.pyc</code> file that contains the bytecode to make importing it again later easier (and faster).</li>
<li><code>.pyo</code>: This was a file format used before Python 3.5 for <code>*.pyc</code> files that were created with optimizations (<code>-O</code>) flag. (see the note below)</li>
<li><code>.pyd</code>: This is basically a windows dll file. <a href="http://docs.python.org/faq/windows.html#is-a-pyd-file-the-same-as-a-dll" rel="noreferrer">http://docs.python.org/faq/windows.html#is-a-pyd-file-the-same-as-a-dll</a></li>
</ol>

Also for some further discussion on <code>.pyc</code> vs <code>.pyo</code>, take a look at: <a href="https://web.archive.org/web/20160130165632/http://www.network-theory.co.uk/docs/pytut/CompiledPythonfiles.html" rel="noreferrer">http://www.network-theory.co.uk/docs/pytut/CompiledPythonfiles.html</a> (I've copied the important part below)

<blockquote>
 <ul>
 <li>When the Python interpreter is invoked with the -O flag, optimized code is generated and stored in ‘.pyo’ files. The optimizer currently doesn't help much; it only removes assert statements. When -O is used, all bytecode is optimized; .pyc files are ignored and .py files are compiled to optimized bytecode.</li>
 <li>Passing two -O flags to the Python interpreter (-OO) will cause the bytecode compiler to perform optimizations that could in some rare cases result in malfunctioning programs. Currently only <code>__doc__</code> strings are removed from the bytecode, resulting in more compact ‘.pyo’ files. Since some programs may rely on having these available, you should only use this option if you know what you're doing.</li>
 <li>A program doesn't run any faster when it is read from a ‘.pyc’ or ‘.pyo’ file than when it is read from a ‘.py’ file; the only thing that's faster about ‘.pyc’ or ‘.pyo’ files is the speed with which they are loaded.</li>
 <li>When a script is run by giving its name on the command line, the bytecode for the script is never written to a ‘.pyc’ or ‘.pyo’ file. Thus, the startup time of a script may be reduced by moving most of its code to a module and having a small bootstrap script that imports that module. It is also possible to name a ‘.pyc’ or ‘.pyo’ file directly on the command line.</li>
 </ul>
</blockquote>

Note: 

On 2015-09-15 the <a href="https://docs.python.org/3/whatsnew/3.5.html#pep-488-elimination-of-pyo-files" rel="noreferrer">Python 3.5 release</a> implemented PEP-488 and eliminated <code>.pyo</code> files. 
This means that <code>.pyc</code> files represent both unoptimized and optimized bytecode.

blocks|key|242596|text|type|unstyled|depth|inlineStyleRanges|entityRanges|data|242597|.py+-常规script|unordered-list-item|offset|length|style|BOLD|242598|.py3+-(很少使用)+Python3脚本。Python脚本通常以“pyc”结尾，而不是“Python”，但我看到一些times|242599|.pyc编译的脚本(Bytecode)|242600|.pyo优化的pyc文件(从Python3.5开始，Python将只使用pyc而不是pyo和pyc)|242601|.pyw+-.py3脚本在窗口模式下运行，没有控制台；使用pythonw.exe|242602|.pyx+-+Cython+src执行，转换为C/C%2B%2B|242603|.pyd+-+Python脚本，作为DLL|242604|.pxd+-+Cython脚本，相当于C/C%2B%2B+header|242605|.pxi+-+Stub+stub|242606|.pyi+-Stub文件(PEP+484)|242607|.pyz+-+Python脚本存档(PEP+441)；这是一个包含标准Python脚本header|242608|.pycod之后的二进制形式的压缩Python脚本(PEP+441)；这是一个包含标准Python脚本header|242609|.pycod之后的二进制形式的压缩Python脚本(PEP+441)-+".gitignore“中的通配符表示法，这意味着该文件可以是".pyc”、".pyo“或".pyd".|242610|.pth+-一个路径配置文件；它的内容是要添加到sys.path的附加项(每行一个)。请参阅|CODE|242611|中的site模块|242612|在http://dcjtech.info/topic/python-file-extensions/上可以找到其他Python文件扩展名的更大列表(大多数是罕见的和非官方的|242613|entityMap|0|LINK|mutability|MUTABLE|url|https://www.python.org/dev/peps/pep-0484/#stub-files|1|https://www.python.org/dev/peps/pep-0441/|2|3|4|https://docs.python.org/3/library/site.html#module-site|5|http://dcjtech.info/topic/python-file-extensions/^0|0|0|3|0|0|4|0|0|4|0|0|4|0|0|4|0|0|4|0|0|4|0|0|4|0|0|4|0|0|4|D|7|0|0|0|4|I|7|1|0|0|6|Q|7|2|0|0|6|Q|7|3|0|0|4|O|8|0|2|4|2|4|4|0|1|1D|5|0^^$0|@$1|2|3|-4|4|5|6|1S|7|@]|8|@]|9|$]]|$1|A|3|B|4|C|6|1T|7|@$D|1U|E|1V|F|G]]|8|@]|9|$]]|$1|H|3|I|4|C|6|1W|7|@$D|1X|E|1Y|F|G]]|8|@]|9|$]]|$1|J|3|K|4|C|6|1Z|7|@$D|20|E|21|F|G]]|8|@]|9|$]]|$1|L|3|M|4|C|6|22|7|@$D|23|E|24|F|G]]|8|@]|9|$]]|$1|N|3|O|4|C|6|25|7|@$D|26|E|27|F|G]]|8|@]|9|$]]|$1|P|3|Q|4|C|6|28|7|@$D|29|E|2A|F|G]]|8|@]|9|$]]|$1|R|3|S|4|C|6|2B|7|@$D|2C|E|2D|F|G]]|8|@]|9|$]]|$1|T|3|U|4|C|6|2E|7|@$D|2F|E|2G|F|G]]|8|@]|9|$]]|$1|V|3|W|4|C|6|2H|7|@$D|2I|E|2J|F|G]]|8|@]|9|$]]|$1|X|3|Y|4|C|6|2K|7|@$D|2L|E|2M|F|G]]|8|@$D|2N|E|2O|1|2P]]|9|$]]|$1|Z|3|10|4|C|6|2Q|7|@$D|2R|E|2S|F|G]]|8|@$D|2T|E|2U|1|2V]]|9|$]]|$1|11|3|12|4|C|6|2W|7|@$D|2X|E|2Y|F|G]]|8|@$D|2Z|E|30|1|31]]|9|$]]|$1|13|3|14|4|C|6|32|7|@$D|33|E|34|F|G]]|8|@$D|35|E|36|1|37]]|9|$]]|$1|15|3|16|4|C|6|38|7|@$D|39|E|3A|F|G]|$D|3B|E|3C|F|17]]|8|@]|9|$]]|$1|18|3|19|4|5|6|3D|7|@$D|3E|E|3F|F|17]]|8|@$D|3G|E|3H|1|3I]]|9|$]]|$1|1A|3|1B|4|5|6|3J|7|@]|8|@$D|3K|E|3L|1|3M]]|9|$]]|$1|1C|3|-4|4|5|6|3N|7|@]|8|@]|9|$]]]|1D|$1E|$4|1F|1G|1H|9|$1I|1J]]|1K|$4|1F|1G|1H|9|$1I|1L]]|1M|$4|1F|1G|1H|9|$1I|1L]]|1N|$4|1F|1G|1H|9|$1I|1L]]|1O|$4|1F|1G|1H|9|$1I|1P]]|1Q|$4|1F|1G|1H|9|$1I|1R]]]]

<ul>
<li>.py - Regular script</li>
<li>.py3 - (rarely used) Python3 script. Python3 scripts usually end with ".py" not ".py3", but I have seen that a few times</li>
<li>.pyc - compiled script (Bytecode)</li>
<li>.pyo - optimized pyc file (As of Python3.5, Python will only use pyc rather than pyo and pyc)</li>
<li>.pyw - Python script to run in Windowed mode, without a console; executed with pythonw.exe</li>
<li>.pyx - Cython src to be converted to C/C++</li>
<li>.pyd - Python script made as a Windows DLL</li>
<li>.pxd - Cython script which is equivalent to a C/C++ header</li>
<li>.pxi - MyPy stub</li>
<li>.pyi - Stub file (<a href="https://www.python.org/dev/peps/pep-0484/#stub-files" rel="noreferrer">PEP 484</a>)</li>
<li>.pyz - Python script archive (<a href="https://www.python.org/dev/peps/pep-0441/" rel="noreferrer">PEP 441</a>); this is a script containing compressed Python scripts (ZIP) in binary form after the standard Python script header</li>
<li>.pywz - Python script archive for MS-Windows (<a href="https://www.python.org/dev/peps/pep-0441/" rel="noreferrer">PEP 441</a>); this is a script containing compressed Python scripts (ZIP) in binary form after the standard Python script header</li>
<li>.py[cod] - wildcard notation in ".gitignore" that means the file may be ".pyc", ".pyo", or ".pyd".</li>
<li>.pth - a path configuration file; its contents are additional items (one per line) to be added to <code>sys.path</code>. See <a href="https://docs.python.org/3/library/site.html#module-site" rel="noreferrer"><code>site</code></a> module.</li>
</ul>

A larger list of additional Python file-extensions (mostly rare and unofficial) can be found at <a href="http://dcjtech.info/topic/python-file-extensions/" rel="noreferrer">http://dcjtech.info/topic/python-file-extensions/</a>

What do these python file extensions mean?

<ul>
<li>.pyc</li>
<li>.pyd</li>
<li>.pyo</li>
</ul>

What are the differences between them and how are they generated from a *.py file?

What do the python file extensions, .pyc .pyd .pyo stand for?

编译器

解释器

Python

这些python文件扩展名是什么意思？.pyc.pyd.pyo它们之间有什么区别?它们是如何从*.py文件中生成的？

问python文件扩展名.pyc .pyd .pyo代表什么？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问python文件扩展名.pyc .pyd .pyo代表什么？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问python文件扩展名.pyc .pyd .pyo代表什么？
EN