下面是如何在Visual Studio Code中配置任务运行器以运行.py文件。

在控制台中，按Ctrl + Shift + P (Windows)或Cmd + Shift + P (Apple)。这将出现一个搜索框，您可以在其中搜索“配置任务运行器”

如果这是第一次打开“任务:配置任务运行器”，则需要在下一个选择列表底部选择“其他”。

这将打开属性，然后您可以更改以适应您的偏好。在本例中，您希望更改以下属性;

将Command属性从"tsc" (TypeScript)更改为"Python" 将showOutput从"silent"修改为"Always" 将args (Arguments)从["Helloworld. "Ts "]到["${文件}"](文件名) 删除最后一个属性problemMatcher 保存所做的更改

您现在可以打开您的.py文件，并使用快捷键Ctrl + Shift + B (Windows)或Cmd + Shift + B (Apple)很好地运行它。

我使用Python 3.7(32位)。要在Visual Studio Code中运行程序，我右键单击程序并选择“在Python交互式窗口中运行当前文件”。如果你没有Jupyter，你可能会被要求安装它。

您可以添加一个自定义任务来完成此任务。下面是Python的一个基本自定义任务。

{
    "version": "0.1.0",
    "command": "c:\\Python34\\python",
    "args": ["app.py"],
    "problemMatcher": {
        "fileLocation": ["relative", "${workspaceRoot}"],
        "pattern": {
            "regexp": "^(.*)+s$",
            "message": 1
        }
    }
}

将其添加到文件任务中。并按Ctrl + Shift + B运行它。

下面是如何在Visual Studio Code中配置任务运行器以运行.py文件。

在控制台中，按Ctrl + Shift + P (Windows)或Cmd + Shift + P (Apple)。这将出现一个搜索框，您可以在其中搜索“配置任务运行器”

如果这是第一次打开“任务:配置任务运行器”，则需要在下一个选择列表底部选择“其他”。

这将打开属性，然后您可以更改以适应您的偏好。在本例中，您希望更改以下属性;

将Command属性从"tsc" (TypeScript)更改为"Python" 将showOutput从"silent"修改为"Always" 将args (Arguments)从["Helloworld. "Ts "]到["${文件}"](文件名) 删除最后一个属性problemMatcher 保存所做的更改

您现在可以打开您的.py文件，并使用快捷键Ctrl + Shift + B (Windows)或Cmd + Shift + B (Apple)很好地运行它。

为了扩展vlad2135的答案(阅读他的第一个);这就是如何在Visual Studio Code中使用Don Jayamanne的Python扩展来设置Python调试(这是目前Python的一个功能非常全面的IDE，并且可以说是Visual Studio Code中最好的语言扩展之一，我认为)。

基本上，当你点击齿轮图标时，它会创建一个启动。Json文件在你的工作空间的。vscode目录。您也可以自己做这个，但是让Visual Studio Code来做这些繁重的工作可能会更简单。下面是一个示例文件:

生成后，您会注意到一些很酷的东西。它自动创建了一堆配置(我的大部分配置都被切断了;只要滚动就能全部看到)，针对不同的库或环境(比如Django)有不同的设置和额外的功能。

你最终使用最多的可能是Python;这是一个简单的(在我的例子中是C)Python调试器，最容易使用设置。

我将对这个JSON属性做一个简短的介绍，因为其他的JSON属性使用几乎相同的配置，只是有不同的解释器路径和一两个不同的其他特性。

name: The name of the configuration. A useful example of why you would change it is if you have two Python configurations which use the same type of config, but different arguments. It's what shows up in the box you see on the top left (my box says "python" since I'm using the default Python configuration). type: Interpreter type. You generally don't want to change this one. request: How you want to run your code, and you generally don't want to change this one either. Default value is "launch", but changing it to "attach" allows the debugger to attach to an already running Python process. Instead of changing it, add a configuration of type attach and use that. stopOnEntry: Python debuggers like to have an invisible break-point when you start the program so you can see the entry-point file and where your first line of active code is. It drives some C#/Java programmers like me insane. false if you don't want it, true otherwise. pythonPath: The path to your install of Python. The default value gets the extension level default in the user/workspace settings. Change it here if you want to have different Pythons for different debug processes. Change it in workspace settings if you want to change it for all debug processes set to the default configuration in a project. Change it in user setting to change where the extension finds Pythons across all projects. (4/12/2017 The following was fixed in extension version 0.6.1). Ironically enough, this gets auto-generated wrong. It auto-generates to "${config.python.pythonPath}" which is deprecated in the newer Visual Studio Code versions. It might still work, but you should use "${config:python.pythonPath}" instead for your default first python on your path or Visual Studio Code settings. (4/6/2017 Edit: This should be fixed in the next release. The team committed the fix a few days ago.) program: The initial file that you debugger starts up when you hit run. "${workspaceRoot}" is the root folder you opened up as your workspace (When you go over to the file icon, the base open folder). Another neat trick if you want to get your program running quickly, or you have multiple entry points to your program is to set this to "${file}" which will start debugging at the file you have open and in focus in the moment you hit debug. cwd: The current working directory folder of the project you're running. Usually you'll just want to leave this "${workspaceRoot}". debugOptions: Some debugger flags. The ones in the picture are default flags, you can find more flags in the python debugger pages, I'm sure. args: This isn't actually a default configuration setting, but a useful one nonetheless (and probably what the OP was asking about). These are the command line arguments that you pass in to your program. The debugger passes these in as though they you had typed: python file.py [args] into your terminal; passing each JSON string in the list to the program in order.

有关Visual Studio Code文件变量的更多信息，可用于配置调试器和路径。

您可以到这里查看扩展自己的启动选项文档，包括可选属性和必选属性。

如果文件中没有配置模板，可以单击右下角的Add Configuration按钮。它将为您提供一个列表，以便为大多数常见的调试过程自动生成配置。

现在，根据vlad的回答，您可以按照正常的可视化调试器添加任何您需要的断点，在左上角的下拉菜单中选择您想要的运行配置，您可以点击配置名称左侧的绿色箭头来启动您的程序。

专业提示:团队中不同的人使用不同的ide，他们可能不需要您的配置文件。Visual Studio Code几乎总是把它的IDE文件放在一个地方(设计为这个目的;如果这是你第一次生成Visual Studio Code文件，请确保将.vscode/目录添加到你的.gitignore中(如果你还没有这个文件，这个过程将在你的工作空间中创建文件夹)!

如果你有一个由多个Python文件组成的项目，并且你想用主程序开始运行/调试，而不依赖于当前的哪个文件，你可以创建以下启动配置(将MyMain.py更改为你的主文件)。

{
  "version": "0.2.0",
  "configurations": [
    {
      "name": "Python: Main File",
      "type": "python",
      "request": "launch",
      "program": "${workspaceFolder}/MyMain.py",
      "console": "integratedTerminal",
      "cwd": "${workspaceFolder}"
    }
  ]
}