First off, interpreted/compiled is not a property of the language but a property of the implementation. For most languages, most if not all implementations fall in one category, so one might save a few words saying the language is interpreted/compiled too, but it's still an important distinction, both because it aids understanding and because there are quite a few languages with usable implementations of both kinds (mostly in the realm of functional languages, see Haskell and ML). In addition, there are C interpreters and projects that attempt to compile a subset of Python to C or C++ code (and subsequently to machine code).

Second, compilation is not restricted to ahead-of-time compilation to native machine code. A compiler is, more generally, a program that converts a program in one programming language into a program in another programming language (arguably, you can even have a compiler with the same input and output language if significant transformations are applied). And JIT compilers compile to native machine code at runtime, which can give speed very close to or even better than ahead of time compilation (depending on the benchmark and the quality of the implementations compared).

But to stop nitpicking and answer the question you meant to ask: Practically (read: using a somewhat popular and mature implementation), Python is compiled. Not compiled to machine code ahead of time (i.e. "compiled" by the restricted and wrong, but alas common definition), "only" compiled to bytecode, but it's still compilation with at least some of the benefits. For example, the statement a = b.c() is compiled to a byte stream which, when "disassembled", looks somewhat like load 0 (b); load_str 'c'; get_attr; call_function 0; store 1 (a). This is a simplification, it's actually less readable and a bit more low-level - you can experiment with the standard library dis module and see what the real deal looks like. Interpreting this is faster than interpreting from a higher-level representation.

字节码要么被解释(请注意，在理论和实际性能上，直接解释和首先编译为一些中间表示并解释它之间存在差异)，就像参考实现(CPython)一样，要么在运行时被解释并编译为优化的机器代码，就像PyPy一样。

这真的取决于所使用的语言的实现!不过，在任何实现中都有一个常见的步骤:您的代码首先被编译(翻译)为中间代码——介于您的代码和机器(二进制)代码之间的东西——称为字节码(存储在.pyc文件中)。注意，这是一个一次性步骤，除非修改代码，否则不会重复。

这个字节码在每次运行程序时都会被执行。怎么做?当我们运行程序时，这个字节码(在.pyc文件中)作为输入传递给虚拟机(VM)1——允许我们的程序被执行的运行时引擎——由虚拟机执行。

根据语言实现，VM将解释字节码(在CPython2实现的情况下)或JIT-compile3字节码(在PyPy4实现的情况下)。

注:

计算机系统的模拟

2字节码解释器;该语言的参考实现，用C和Python编写，使用最广泛

在程序执行期间(在运行时)进行的3个编译

4字节码JIT编译器;CPython的替代实现，用RPython (Restricted Python)编写——通常比CPython运行得更快

如果(你懂Java) { Python代码像java一样被转换成字节码。 每次您尝试访问该字节码时，都会再次执行它。 }其他{ Python代码最初被翻译成一种叫做字节码的东西 接近机器语言，但不是真正的机器代码 因此，每次我们访问或运行它时，字节码都会再次执行 ｝

答案取决于使用的是哪种python实现。如果你正在使用CPython (python的标准实现)或Jython(用于与java编程语言集成)，它首先被翻译成字节码，并根据你正在使用的python实现，这个字节码被定向到相应的虚拟机进行解释。PVM (Python虚拟机)用于CPython, JVM (Java虚拟机)用于Jython。

但假设你使用的是PyPy，这是另一个标准的CPython实现。它将使用即时编译器。

这似乎是语义上的问题。我想大多数人都会推断编译的结果通常是机器代码。考虑到这一点，我对自己说，python是没有编译的。不过我可能错了，因为compile实际上意味着转换到较低级别，所以从源代码转换到字节码也是编译。

对于新手

在运行脚本之前，Python会自动将脚本编译为已编译的代码，即所谓的字节代码。

运行脚本不被认为是导入，也不会创建.pyc。

例如，如果你有一个脚本文件abc.py，它导入了另一个模块xyz.py，当你运行abc.py时，xyz.py, xyz.py。Pyc将被创建，因为xyz被导入，但没有abc。Pyc文件将被创建，因为abc.py没有被导入。