所有脚本语言都是编程语言。

语言并不被归类为脚本——这完全取决于执行环境。

如果环境是解释环境，则通常称为脚本环境。

脚本语言

脚本语言是在另一个程序中解释的。JavaScript被嵌入到浏览器中，并由该浏览器进行解释。

脚本语言示例

JavaScript Perl Python

脚本语言的优点:

简单——脚本语言比编程更容易编写 语言。 更少的代码行数

编程语言

像Java这样的编程语言是由另一个应用程序以同样的方式编译和解释的。

编程语言示例

C c++和 Java

更多的细节

http://www.yorku.ca/nmw/facs1939f13/javascript_all/js_scriptingVSprogramming.html http://www.killersites.com/blog/2005/scripting-vs-programming-is-there-a-difference/

这些差异正变得越来越不重要。传统上，脚本语言扩展了现有的程序……我认为这就是“脚本”的主要定义，它指的是为现有实体编写一组执行指令。然而，脚本语言起源于专有的和口语化的语法，现在流行的大多数脚本语言都与C有某种关系。

I think the "interpreted vs compiled" distinction is really a symptom of extending an existing program (with a built in interpreter), rather than an intrinsic difference. What programmers and laymen are more concerned about is, "what is the programmer doing?" The fact that one program is interpreted and another is compiled means very little in determining the difference in activity by the creator. You don't judge a playwright on whether his plays are more commonly read aloud or performed on stage, do you?

编程语言: 编译为机器码并在底层操作系统的硬件上运行。

脚本语言: 是编程语言的非结构子集。这是一般的解释。 它基本上是“脚本”其他事情来做事情。主要的重点不是构建你自己的应用程序，而是让现有的应用程序以你想要的方式运行，例如浏览器的JavaScript, TCL等。

***但也有编程语言被转换为解释器的情况，反之亦然，比如使用C解释器，你可以使用C脚本。 脚本通常用于控制应用程序的行为，而编程语言则用于构建应用程序。 但要注意的是，这种界限正在日益模糊——作为Python的一个例子，它取决于你如何使用这种语言。

我认为你所说的“差异”实际上是真实差异的结果。

实际的区别在于所编写代码的目标。谁来运行这段代码。

脚本语言用于编写针对软件系统的代码。它将对软件系统进行自动化操作。脚本将是目标软件系统的指令序列。

编程语言的目标是计算系统，可以是真实的也可以是虚拟机。指令是由机器执行的。

当然，真正的机器只理解二进制代码，因此您需要编译编程语言的代码。但这是针对机器而不是程序的结果。

另一方面，脚本的目标软件系统可以编译代码或解释它。由软件系统决定。

如果我们说真正的区别是它是否被编译，那么我们就有一个问题，因为Javascript在V8中运行时是编译的，而在Rhino中运行时不是。

由于脚本语言已经进化得非常强大，所以它变得更加令人困惑。因此，它们不局限于创建小脚本来自动化另一个软件系统上的操作，您可以使用它们创建任何丰富的应用程序。

Python代码以解释器为目标，因此我们可以说它“脚本化”了解释器上的操作。但是，当你编写Python代码时，你不会将其视为编写解释器脚本，而是将其视为创建应用程序。解释器只是用于在更高级别上编写代码。所以对我来说，Python更像是一种编程语言，而不是脚本语言。

在世界还很年轻的时候，在PC世界中，你可以从。exe或。bat中选择，描述很简单。Unix系统一直都有shell脚本(/bin/sh， /bin/csh， /bin/ksh等)和编译语言(C/ c++ /Fortran)。

To differentiate roles and responsibilities, the compiled languages (often referred to as 3rd Generation Languages) were seen a 'programming' languages and 'scripting' languages were seen as those that invoked an interpreter (often referred to as 4th Generation Languages). Scripting languages were often used as 'glue' to connect between multiple commands/compiled programs so that the user didn't have to worry about a set of steps in order to carry out their task - they developed a single file, that delineated what steps they wanted to accomplish, and this became a 'script' for anyone to follow.

Various people/groups wrote new interpreters to solve a specific problem domain. awk is one of the better-known ones, and it was used mostly for pattern matching and applying a series of data transforms on input. It worked well, but had a limited problem domain. The expansion of that domain was all but impossible because the source code was unavailable. Perl (Larry Wall, principle author/architect) tool scripting to the next level - and developed an interpreter that not only allowed the user to run system commands, manipulate input and output data, supported typeless variables, but also to access Unix system level APIs as functions from within the scripts themselves. It was probably one of the first widely used high-level scripting languages. It is with Perl (IMHO) that scripting languages crossed the arbitrary line and added the capabilities of programming languages.

你的问题是关于Python的。因为python解释器是针对包含python代码的文本文件运行的，而且python代码可以在任何有python解释器的地方运行，所以我认为它是一种脚本语言(与Perl相同)。您不需要为每个不同的OS/CPU架构重新编译用户python命令文件(就像使用C/ c++ /Fortran一样)，这使得它更易于移植和使用。

这个答案要归功于杰罗德·海曼(Jerrold Heyman)。 原帖:https://www.researchgate.net/post/Is_Python_a_Programming_language_or_Scripting_Language