How to debug python in visual studio code

How to debug python in visual studio code code#

A configuration file containing your run configuration settings opens in the editor.

Not adding debugpy as a dependency runs your experiment without attaching to the debugger. To add debugpy as a dependency,select Add Debugpy.

Debugpy is required in order to attach the debugger to the container running your experiment.

You can create Azure Machine Learning datasets using the extension.

Choose whether you want to use an Azure Machine Learning dataset or not.

The path is relative to the directory opened in VS Code.

Provide the name of the script you want to run.You can choose from any of the Azure Machine Learning curated or create your own. Alternatively, if you already have one, select it from the dropdown. The run configuration defines the script you want to run, dependencies, and datasets used. Select Create new Run Configuration to create your run configuration. Selecting no will run your experiment locally without attaching to the debugger. Additionally, it also allows Docker to store the logs and outputs from your run in a temporary directory on your system. When you enable file share it allows Docker to mount the directory containing your script to the container. When prompted to allow File Share, select Yes. When the prompt appears, provide a name for your experiment.Д®xpand the Experiments node, right-click the experiment you want to run and select Run Experiment.ДЇrom the list of options to run your experiment, select Locally.ДЇirst time use on Windows only. Right-click the Experiments node and select Create experiment. If you don't already have one, you can create an Azure Machine Learning workspace using the extension. In VS Code, open the Azure Machine Learning extension view.Д®xpand the subscription node containing your workspace.

How to debug python in visual studio code code#

The azureML.CLI Compatibility Mode setting in Visual Studio Code is set to 1.0 as specified in the prerequisites.Before running your experiment locally make sure that: