为什么python在解释之前将源代码编译为字节码?

Why python compile the source to bytecode before interpreting?(为什么python在解释之前将源代码编译为字节码?)
本文介绍了为什么python在解释之前将源代码编译为字节码?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

为什么python在解释之前要把源码编译成字节码?

Why python compile the source to bytecode before interpreting?

为什么不直接从源头解释?

Why not interpret from the source directly?

推荐答案

几乎没有解释器真正直接逐行解释代码——这实在是太低效了.几乎所有解释器都使用一些可以轻松执行的中间表示.此外,还可以对此中间代码进行小幅优化.

Nearly no interpreter really interprets code directly, line by line – it's simply too inefficient. Almost all interpreters use some intermediate representation which can be executed easily. Also, small optimizations can be performed on this intermediate code.

Python 还存储了这段代码,这对下次执行这段代码有很大的好处:Python 不再需要解析代码;解析是编译过程中最慢的部分.因此,字节码表示可以大大减少执行开销.

Python furthermore stores this code which has a huge advantage for the next time this code gets executed: Python doesn't have to parse the code anymore; parsing is the slowest part in the compile process. Thus, a bytecode representation reduces execution overhead quite substantially.

这篇关于为什么python在解释之前将源代码编译为字节码?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持编程学习网!

本站部分内容来源互联网,如果有图片或者内容侵犯您的权益请联系我们删除!

相关文档推荐

Leetcode 234: Palindrome LinkedList(Leetcode 234:回文链接列表)
How do I read an Excel file directly from Dropbox#39;s API using pandas.read_excel()?(如何使用PANDAS.READ_EXCEL()直接从Dropbox的API读取Excel文件?)
subprocess.Popen tries to write to nonexistent pipe(子进程。打开尝试写入不存在的管道)
I want to realize Popen-code from Windows to Linux:(我想实现从Windows到Linux的POpen-code:)
Reading stdout from a subprocess in real time(实时读取子进程中的标准输出)
How to call type safely on a random file in Python?(如何在Python中安全地调用随机文件上的类型?)