Expressions are reevaluated for each step:įor more on using Watch, see Set a watch on variables using the Watch and QuickWatch windows.
CAN YOU CODE PYTHON IN VISUAL STUDIO WINDOWS
The Watch windows ( Debug > Windows > Watch > Watch 1-4) allow you to enter arbitrary Python expressions and view the results. The Locals window ( Debug > Windows > Locals) displays all variables that are in the current scope, which can again be edited:įor more on using Autos and Locals, see Inspect variables in the Autos and Locals windows. You can double-click in the value column or select and press F2 to edit the value: The Autos window ( Debug > Windows > Autos) contains variables and expressions that are close to the current statement. To view a value using DataTips, simply hover the mouse over any variable in the editor. (See Inspect variables for general details.) You can also use the Watch window to monitor individual variables and custom expressions. When stopped in the debugger, you can inspect and modify the values of variables. This command is helpful if you've been looking around in your code and don't remember where the debugger is stopped. Returns you to the next statement to run. This command allows you to omit a segment of code from being run at all, such as when you know the code is faulty or produces an unwanted side-effect. This command allows you to easily skip over a segment of code that you don't need to debug.Ĭhanges the current run point in the code to the location of the caret. Runs code up to the location of the caret in the editor. This command is useful when you don't need to debug the remainder of the current function.
Runs code until the end of the current function, then steps to the calling statement. Stepping over allows you to easily skip functions that you do not need to debug. Runs the next statement, including making a call to a function (running all its code) and applying any return value. If the next statement is a call to a function, the debugger stops at the first line of the function being called. Runs code until the next breakpoint is reached. These commands are available in a number of places, including the top debug toolbar, the Debug menu, on the right-click context menu in the code editor, and through keyboard shortcuts (though not all commands are in all places): Feature Once stopped at a breakpoint, you have various ways to step through code or run blocks of code before breaking again. Logging a message creates what is called a tracepoint without adding logging code to your application directly: When setting conditions, you can also set Action and create a message to log to the output window, optionally continuing execution automatically.
CAN YOU CODE PYTHON IN VISUAL STUDIO FULL
For full details on this feature in Visual Studio, see Breakpoint conditions. To set conditions, right-click the breakpoint's red dot, select Condition, then create expressions using Python code. You can customize the conditions under which a breakpoint is triggered, such as breaking only when a variable is set to a certain value or value range. This behavior is correct, even though it's sometimes surprising. If a breakpoint has been set, you may find the debugger breaking part-way through a class declaration. In Python, the entire file is executable code, so Python runs the file when it's loaded to process any top-level class or function definitions. Some breakpoints in Python can be surprising for developers who have worked with other programming languages. In any case, right-click the appropriate file and select Set as Startup File. Visual Studio 2017 version 15.6 and later alerts you if you don't have a startup file set earlier versions may open an output window with the Python interpreter running, or the output window briefly appears and disappears. These actions launch your project's startup file (shown in bold in Solution Explorer) with the project's active environment and any command-line arguments or search paths that have been specified in Project Properties (see Project debugging options). The basic debugging workflow involves settings breakpoints, stepping through code, inspecting values, and handling exceptions as described in the following sections.Ī debugging session starts with the Debug > Start Debugging command, the Start button on the toolbar, or the F5 key. To control the environment and arguments, create a project for the code, which is easily done with the From existing Python code project template. But from then on, you have full debugging support. With a stand-alone Python file open, right-click in the editor, select Start with Debugging, and Visual Studio launches the script with the global default environment (see Python environments) and no arguments. Python in Visual Studio supports debugging without a project.
0 kommentar(er)
