In this tutorial, you use Python 3 to create the simplest Python 'Hello World' application in Visual Studio Code. By using the Python extension, you make VS Code into a great lightweight Python IDE (which you may find a productive alternative to PyCharm).
- Debug Django Visual Studio Code
- Django In Visual Studio Code
- Visual Studio Code Django Debugging
- Django Projects In Visual Studio Code
This tutorial introduces you to VS Code as a Python environment, primarily how to edit, run, and debug code through the following tasks:
Visual Studio Code is free and available on your favorite platform - Linux, macOS, and Windows. Download Visual Studio Code to experience a redefined code editor, optimized for building and debugging modern web and cloud applications. Django extension for Visual Studio Code. Beautiful syntax and scoped snippets for perfectionists with deadlines. Configure you file association for Django HTML in the Language Mode menu or drop this in your settings for more precision. Setup Visual Studio Code for Django Install Python Extension Install pylint Install autopep8 Django Playlist: https://www.youtube.com/playlist?list=PLbGuiZY. In this case, we open the 8000 for Django runserver and the 8888 so VS Code can connect via the Debug tab to Django. To be able to do this, Microsoft created a library, ptvsd the Python tools for the Visual Studio debugger.This library runs within our Python code. Browse other questions tagged python django macos visual-studio-code or ask your own question. The Overflow Blog Podcast 332: Non-fungible Talking. The Loop: Our Community & Public Platform Roadmap for Q2 2021. Featured on Meta Stack Overflow for Teams is now free for up to 50 users, forever.
Debug Django Visual Studio Code
- Write, run, and debug a Python 'Hello World' Application
- Learn how to install packages by creating Python virtual environments
- Write a simple Python script to plot figures within VS Code
This tutorial is not intended to teach you Python itself. Once you are familiar with the basics of VS Code, you can then follow any of the programming tutorials on python.org within the context of VS Code for an introduction to the language.
If you have any problems, feel free to file an issue for this tutorial in the VS Code documentation repository.
Prerequisites
To successfully complete this tutorial, you need to first setup your Python development environment. Specifically, this tutorial requires:
- VS Code
- VS Code Python extension
- Python 3
Install Visual Studio Code and the Python Extension
If you have not already done so, install VS Code.
Next, install the Python extension for VS Code from the Visual Studio Marketplace. For additional details on installing extensions, see Extension Marketplace. The Python extension is named Python and it's published by Microsoft.
Install a Python interpreter
Along with the Python extension, you need to install a Python interpreter. Which interpreter you use is dependent on your specific needs, but some guidance is provided below.
Windows
Install Python from python.org. You can typically use the Download Python button that appears first on the page to download the latest version.
Note: If you don't have admin access, an additional option for installing Python on Windows is to use the Microsoft Store. The Microsoft Store provides installs of Python 3.7, Python 3.8, and Python 3.9. Be aware that you might have compatibility issues with some packages using this method.
For additional information about using Python on Windows, see Using Python on Windows at Python.org
macOS
The system install of Python on macOS is not supported. Instead, an installation through Homebrew is recommended. To install Python using Homebrew on macOS use brew install python3
at the Terminal prompt.
Note On macOS, make sure the location of your VS Code installation is included in your PATH environment variable. See these setup instructions for more information.
Linux
The built-in Python 3 installation on Linux works well, but to install other Python packages you must install pip
with get-pip.py.
Other options
Data Science: If your primary purpose for using Python is Data Science, then you might consider a download from Anaconda. Anaconda provides not just a Python interpreter, but many useful libraries and tools for data science.
Windows Subsystem for Linux: If you are working on Windows and want a Linux environment for working with Python, the Windows Subsystem for Linux (WSL) is an option for you. If you choose this option, you'll also want to install the Remote - WSL extension. For more information about using WSL with VS Code, see VS Code Remote Development or try the Working in WSL tutorial, which will walk you through setting up WSL, installing Python, and creating a Hello World application running in WSL.
Verify the Python installation
To verify that you've installed Python successfully on your machine, run one of the following commands (depending on your operating system):
Linux/macOS: open a Terminal Window and type the following command:
Windows: open a command prompt and run the following command:
If the installation was successful, the output window should show the version of Python that you installed.
Note You can use the py -0
command in the VS Code integrated terminal to view the versions of python installed on your machine. The default interpreter is identified by an asterisk (*).
Start VS Code in a project (workspace) folder
Using a command prompt or terminal, create an empty folder called 'hello', navigate into it, and open VS Code (code
) in that folder (.
) by entering the following commands:
Note: If you're using an Anaconda distribution, be sure to use an Anaconda command prompt.
By starting VS Code in a folder, that folder becomes your 'workspace'. VS Code stores settings that are specific to that workspace in .vscode/settings.json
, which are separate from user settings that are stored globally.
Alternately, you can run VS Code through the operating system UI, then use File > Open Folder to open the project folder.
Select a Python interpreter
Python is an interpreted language, and in order to run Python code and get Python IntelliSense, you must tell VS Code which interpreter to use.
From within VS Code, select a Python 3 interpreter by opening the Command Palette (⇧⌘P (Windows, Linux Ctrl+Shift+P)), start typing the Python: Select Interpreter command to search, then select the command. You can also use the Select Python Environment option on the Status Bar if available (it may already show a selected interpreter, too):
The command presents a list of available interpreters that VS Code can find automatically, including virtual environments. If you don't see the desired interpreter, see Configuring Python environments.
Note: When using an Anaconda distribution, the correct interpreter should have the suffix ('base':conda)
, for example Python 3.7.3 64-bit ('base':conda)
.
Selecting an interpreter sets the python.pythonPath
value in your workspace settings to the path of the interpreter. To see the setting, select File > Preferences > Settings (Code > Preferences > Settings on macOS), then select the Workspace Settings tab.
Note: If you select an interpreter without a workspace folder open, VS Code sets python.pythonPath
in your user settings instead, which sets the default interpreter for VS Code in general. The user setting makes sure you always have a default interpreter for Python projects. The workspace settings lets you override the user setting.
Create a Python Hello World source code file
From the File Explorer toolbar, select the New File button on the hello
folder:
Name the file hello.py
, and it automatically opens in the editor:
By using the .py
file extension, you tell VS Code to interpret this file as a Python program, so that it evaluates the contents with the Python extension and the selected interpreter.
Note: The File Explorer toolbar also allows you to create folders within your workspace to better organize your code. You can use the New folder button to quickly create a folder.
Now that you have a code file in your Workspace, enter the following source code in hello.py
:
When you start typing print
, notice how IntelliSense presents auto-completion options.
IntelliSense and auto-completions work for standard Python modules as well as other packages you've installed into the environment of the selected Python interpreter. It also provides completions for methods available on object types. For example, because the msg
variable contains a string, IntelliSense provides string methods when you type msg.
:
Feel free to experiment with IntelliSense some more, but then revert your changes so you have only the msg
variable and the print
call, and save the file (⌘S (Windows, Linux Ctrl+S)).
For full details on editing, formatting, and refactoring, see Editing code. The Python extension also has full support for Linting.
Run Hello World
It's simple to run hello.py
with Python. Just click the Run Python File in Terminal play button in the top-right side of the editor.
The button opens a terminal panel in which your Python interpreter is automatically activated, then runs python3 hello.py
(macOS/Linux) or python hello.py
(Windows):
There are three other ways you can run Python code within VS Code:
Right-click anywhere in the editor window and select Run Python File in Terminal (which saves the file automatically):
Select one or more lines, then press Shift+Enter or right-click and select Run Selection/Line in Python Terminal. This command is convenient for testing just a part of a file.
From the Command Palette (⇧⌘P (Windows, Linux Ctrl+Shift+P)), select the Python: Start REPL command to open a REPL terminal for the currently selected Python interpreter. In the REPL, you can then enter and run lines of code one at a time.
Configure and run the debugger
Let's now try debugging our simple Hello World program.
First, set a breakpoint on line 2 of hello.py
by placing the cursor on the print
call and pressing F9. Alternately, just click in the editor's left gutter, next to the line numbers. When you set a breakpoint, a red circle appears in the gutter.
Next, to initialize the debugger, press F5. Since this is your first time debugging this file, a configuration menu will open from the Command Palette allowing you to select the type of debug configuration you would like for the opened file.
Note: VS Code uses JSON files for all of its various configurations; launch.json
is the standard name for a file containing debugging configurations.
These different configurations are fully explained in Debugging configurations; for now, just select Python File, which is the configuration that runs the current file shown in the editor using the currently selected Python interpreter.
The debugger will stop at the first line of the file breakpoint. The current line is indicated with a yellow arrow in the left margin. If you examine the Local variables window at this point, you will see now defined msg
variable appears in the Local pane.
A debug toolbar appears along the top with the following commands from left to right: continue (F5), step over (F10), step into (F11), step out (⇧F11 (Windows, Linux Shift+F11)), restart (⇧⌘F5 (Windows, Linux Ctrl+Shift+F5)), and stop (⇧F5 (Windows, Linux Shift+F5)).
The Status Bar also changes color (orange in many themes) to indicate that you're in debug mode. The Python Debug Console also appears automatically in the lower right panel to show the commands being run, along with the program output.
To continue running the program, select the continue command on the debug toolbar (F5). The debugger runs the program to the end.
Tip Debugging information can also be seen by hovering over code, such as variables. In the case of msg
, hovering over the variable will display the string Hello world
in a box above the variable.
You can also work with variables in the Debug Console (If you don't see it, select Debug Console in the lower right area of VS Code, or select it from the ... menu.) Then try entering the following lines, one by one, at the > prompt at the bottom of the console:
Select the blue Continue button on the toolbar again (or press F5) to run the program to completion. 'Hello World' appears in the Python Debug Console if you switch back to it, and VS Code exits debugging mode once the program is complete.
If you restart the debugger, the debugger again stops on the first breakpoint.
To stop running a program before it's complete, use the red square stop button on the debug toolbar (⇧F5 (Windows, Linux Shift+F5)), or use the Run > Stop debugging menu command.
For full details, see Debugging configurations, which includes notes on how to use a specific Python interpreter for debugging.
Tip: Use Logpoints instead of print statements: Developers often litter source code with print
statements to quickly inspect variables without necessarily stepping through each line of code in a debugger. In VS Code, you can instead use Logpoints. A Logpoint is like a breakpoint except that it logs a message to the console and doesn't stop the program. For more information, see Logpoints in the main VS Code debugging article.
Install and use packages
Let's now run an example that's a little more interesting. In Python, packages are how you obtain any number of useful code libraries, typically from PyPI. For this example, you use the matplotlib
and numpy
packages to create a graphical plot as is commonly done with data science. (Note that matplotlib
cannot show graphs when running in the Windows Subsystem for Linux as it lacks the necessary UI support.)
Return to the Explorer view (the top-most icon on the left side, which shows files), create a new file called standardplot.py
, and paste in the following source code:
Tip: If you enter the above code by hand, you may find that auto-completions change the names after the as
keywords when you press Enter at the end of a line. To avoid this, type a space, then Enter.
Next, try running the file in the debugger using the 'Python: Current file' configuration as described in the last section.
Unless you're using an Anaconda distribution or have previously installed the matplotlib
package, you should see the message, 'ModuleNotFoundError: No module named 'matplotlib'. Such a message indicates that the required package isn't available in your system.
To install the matplotlib
package (which also installs numpy
as a dependency), stop the debugger and use the Command Palette to run Terminal: Create New Integrated Terminal (⌃⇧` (Windows, Linux Ctrl+Shift+`)). This command opens a command prompt for your selected interpreter.
A best practice among Python developers is to avoid installing packages into a global interpreter environment. You instead use a project-specific virtual environment
that contains a copy of a global interpreter. Once you activate that environment, any packages you then install are isolated from other environments. Such isolation reduces many complications that can arise from conflicting package versions. To create a virtual environment and install the required packages, enter the following commands as appropriate for your operating system:
Note: For additional information about virtual environments, see Environments.
Create and activate the virtual environment
Note: When you create a new virtual environment, you should be prompted by VS Code to set it as the default for your workspace folder. If selected, the environment will automatically be activated when you open a new terminal.
For Windows
If the activate command generates the message 'Activate.ps1 is not digitally signed. You cannot run this script on the current system.', then you need to temporarily change the PowerShell execution policy to allow scripts to run (see About Execution Policies in the PowerShell documentation):
For macOS/Linux
Select your new environment by using the Python: Select Interpreter command from the Command Palette.
Install the packages
Rerun the program now (with or without the debugger) and after a few moments a plot window appears with the output:
Once you are finished, type
deactivate
in the terminal window to deactivate the virtual environment.
For additional examples of creating and activating a virtual environment and installing packages, see the Django tutorial and the Flask tutorial.
Next steps
You can configure VS Code to use any Python environment you have installed, including virtual and conda environments. You can also use a separate environment for debugging. For full details, see Environments.
To learn more about the Python language, follow any of the programming tutorials listed on python.org within the context of VS Code.
To learn to build web apps with the Django and Flask frameworks, see the following tutorials:
There is then much more to explore with Python in Visual Studio Code:
- Editing code - Learn about autocomplete, IntelliSense, formatting, and refactoring for Python.
- Linting - Enable, configure, and apply a variety of Python linters.
- Debugging - Learn to debug Python both locally and remotely.
- Testing - Configure test environments and discover, run, and debug tests.
- Settings reference - Explore the full range of Python-related settings in VS Code.
Python is a popular programming language that is reliable, flexible, easy to learn, free to use on all operating systems, and supported by both a strong developer community and many free libraries. Python supports all manners of development, including web applications, web services, desktop apps, scripting, and scientific computing, and is used by many universities, scientists, casual developers, and professional developers alike. You can learn more about the language on python.org and Python for Beginners.
Visual Studio is a powerful Python IDE on Windows. Visual Studio provides open-source support for the Python language through the Python Development and Data Science workloads (Visual Studio 2017 and later) and the free Python Tools for Visual Studio extension (Visual Studio 2015 and earlier).
Python is not presently supported in Visual Studio for Mac, but is available on Mac and Linux through Visual Studio Code (see questions and answers).
To get started:
- Follow the installation instructions to set up the Python workload.
- Familiarize yourself with the Python capabilities of Visual Studio through the sections in this article.
- Go through one or more of the Quickstarts to create a project. If you're unsure, start with Create a web app with Flask.
- Go through one or more of the Quickstarts to create a project. If you're unsure, start with Quickstart: Open and run Python code in a folder or Create a web app with Flask.
- Follow the Work with Python in Visual Studio tutorial for a full end-to-end experience.
Note
Visual Studio supports Python version 2.7, as well as version 3.5 through 3.7. While it is possible to use Visual Studio to edit code written in other versions of Python, those versions are not officially supported and features such as IntelliSense and debugging might not work. Python version 3.8 support is still under development, specific details about support can be seen in this tracking issue on GitHub.
Support for multiple interpreters
Django In Visual Studio Code
Visual Studio's Python Environments window (shown below in a wide, expanded view) gives you a single place to manage all of your global Python environments, conda environments, and virtual environments. Visual Studio automatically detects installations of Python in standard locations, and allows you to configure custom installations. With each environment, you can easily manage packages, open an interactive window for that environment, and access environment folders.
Use the Open interactive window command to run Python interactively within the context of Visual Studio. Use the Open in PowerShell command to open a separate command window in the folder of the selected environment. From that command window you can run any python script.
For more information:
Rich editing, IntelliSense, and code comprehension
Visual Studio provides a first-class Python editor, including syntax coloring, auto-complete across all your code and libraries, code formatting, signature help, refactoring, linting, and type hints. Visual Studio also provides unique features like class view, Go to Definition, Find All References, and code snippets. Direct integration with the Interactive window helps you quickly develop Python code that's already saved in a file.
For more information:
- Docs: Edit Python code
- Docs: Format code
- Docs: Refactor code
- Docs: Use a linter
- General Visual Studio feature docs: Features of the code editor
Interactive window
For every Python environment known to Visual Studio, you can easily open the same interactive (REPL) environment for a Python interpreter directly within Visual Studio, rather than using a separate command prompt. You can easily switch between environments as well. (To open a separate command prompt, select your desired environment in the Python Environments window, then select the Open in PowerShell command as explained earlier under Support for multiple interpreters.)
Visual Studio also provides tight integration between the Python code editor and the Interactive window. The Ctrl+Enter keyboard shortcut conveniently sends the current line of code (or code block) in the editor to the Interactive window, then moves to the next line (or block). Ctrl+Enter lets you easily step through code without having to run the debugger. You can also send selected code to the Interactive window with the same keystroke, and easily paste code from the Interactive window into the editor. Together, these capabilities allow you to work out details for a segment of code in the Interactive window and easily save the results in a file in the editor.
Visual Studio also supports IPython/Jupyter in the REPL, including inline plots, .NET, and Windows Presentation Foundation (WPF).
For more information:
Project system, and project and item templates
Note
Visual Studio 2019 supports opening a folder containing Python code and running that code without creating Visual Studio project and solution files. For more information, see Quickstart: Open and run Python code in a folder. There are, however, benefits to using a project file, as explained in this section.
Visual Studio helps you manage the complexity of a project as it grows over time. A Visual Studio project is much more than a folder structure: it includes an understanding of how different files are used and how they relate to each other. Visual Studio helps you distinguish app code, test code, web pages, JavaScript, build scripts, and so on, which then enable file-appropriate features. A Visual Studio solution, moreover, helps you manage multiple related projects, such as a Python project and a C++ extension project.
Project and item templates automate the process of setting up different types of projects and files, saving you valuable time and relieving you from managing intricate and error-prone details. Visual Studio provides templates for web, Azure, data science, console, and other types of projects, along with templates for files like Python classes, unit tests, Azure web configuration, HTML, and even Django apps.
For more information:
- Docs: Manage Python projects
- Docs: Item templates reference
- Docs: Python project templates
- Docs: Work with C++ and Python
- General Visual Studio feature docs: Project and item templates
- General Visual Studio feature docs: Solutions and projects in Visual Studio
Full-featured debugging
One of Visual Studio's strengths is its powerful debugger. For Python in particular, Visual Studio includes Python/C++ mixed-mode debugging, remote debugging on Linux, debugging within the Interactive window, and debugging Python unit tests.
In Visual Studio 2019, you can run and debug code without having a Visual Studio project file. See Quickstart: Open and run Python code in a folder for an example.
For more information:
- Docs: Debug Python
- Docs: Python/C++ mixed-mode debugging
- Docs: Remote debugging on Linux
- General Visual Studio feature docs: Feature tour of the Visual Studio Debugger
Profiling tools with comprehensive reporting
Profiling explores how time is being spent within your application. Visual Studio supports profiling with CPython-based interpreters and includes the ability to compare performance between different profiling runs.
For more information:
- Docs: Python profiling tools
- General Visual Studio feature docs: Profiling Feature Tour. (Not all Visual Studio profiling features are available for Python).
Unit testing tools
Discover, run, and manage tests in Visual Studio Test Explorer, and easily debug unit tests.
For more information:
- Docs: Unit testing tools for Python
- General Visual Studio feature docs: Unit test your code.
Azure SDK for Python
The Azure libraries for Python simplify consuming Azure services from Windows, Mac OS X, and Linux apps. You can use them to create and manage Azure resources, as well as to connect to Azure services.
For more information, see Azure SDK for Python and Azure libraries for Python.
Questions and answers
Q. Is Python support available with Visual Studio for Mac?
A. Not at this time, but you can up vote the request on Developer Community. The Visual Studio for Mac documentation identifies the current types of development that it does support. In the meantime, Visual Studio Code on Windows, Mac, and Linux works well with Python through available extensions.
Q. What can I use to build UI with Python?
A. The main offering in this area is the Qt Project, with bindings for Python known as PySide (the official binding) (also see PySide downloads) and PyQt. At present, Python support in Visual Studio does not include any specific tools for UI development.
Q. Can a Python project produce a stand-alone executable?
A. Python is generally an interpreted language, with which code is run on demand in a suitable Python-capable environment such as Visual Studio and web servers. Visual Studio itself does not at present provide the means to create a stand-alone executable, which essentially means a program with an embedded Python interpreter. However, the Python community supplied different means to create executables as described on StackOverflow. CPython also supports being embedded within a native application, as described on the blog post, Using CPython's embeddable zip file.
Feature support
Python features can be installed in the following editions of Visual Studio as described in the installation guide:
- Visual Studio 2017 (all editions)
- Visual Studio 2015 (all editions)
- Visual Studio 2013 Community Edition
- Visual Studio 2013 Express for Web, Update 2 or higher
- Visual Studio 2013 Express for Desktop, Update 2 or higher
- Visual Studio 2013 (Pro edition or higher)
- Visual Studio 2012 (Pro edition or higher)
- Visual Studio 2010 SP1 (Pro edition or higher; .NET 4.5 required)
Visual Studio 2015 and earlier are available at visualstudio.microsoft.com/vs/older-downloads/.
Important
Features are fully supported and maintained for only the latest version of Visual Studio. Features are available in older versions but are not actively maintained.
Python support | 2017+ | 2015 | 2013 Comm | 2013 Desktop | 2013 Web | 2013 Pro+ | 2012 Pro+ | 2010 SP1 Pro+ |
---|---|---|---|---|---|---|---|---|
Manage multiple interpreters | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
Auto-detect popular interpreters | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
Add custom interpreters | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
Virtual Environments | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
Pip/Easy Install | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
Project system | 2017+ | 2015 | 2013 Comm | 2013 Desktop | 2013 Web | 2013 Pro+ | 2012 Pro+ | 2010 SP1 Pro+ |
---|---|---|---|---|---|---|---|---|
New project from existing code | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
Show all files | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
Source control | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
Git integration | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔1 | ✗ |
Editing | 2017+ | 2015 | 2013 Comm | 2013 Desktop | 2013 Web | 2013 Pro+ | 2012 Pro+ | 2010 SP1 Pro+ |
---|---|---|---|---|---|---|---|---|
Syntax highlighting | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
Auto-complete | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
Signature help | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
Quick info | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
Object browser/class view | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
Navigation bar | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
Go to Definition | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
Navigate to | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
Find All References | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
Auto indentation | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
Code formatting | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
Refactor - rename | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
Refactor - extract method | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
Refactor - add/remove import | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
PyLint | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
Interactive window | 2017+ | 2015 | 2013 Comm | 2013 Desktop | 2013 Web | 2013 Pro+ | 2012 Pro+ | 2010 SP1 Pro+ |
---|---|---|---|---|---|---|---|---|
Interactive window | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
IPython with inline graphs | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
Visual Studio Code Django Debugging
Desktop | 2017+ | 2015 | 2013 Comm | 2013 Desktop | 2013 Web | 2013 Pro+ | 2012 Pro+ | 2010 SP1 Pro+ |
---|---|---|---|---|---|---|---|---|
Console/Windows application | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
IronPython WPF (with XAML designer) | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
IronPython Windows Forms | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
Web | 2017+ | 2015 | 2013 Comm | 2013 Desktop | 2013 Web | 2013 Pro+ | 2012 Pro+ | 2010 SP1 Pro+ |
---|---|---|---|---|---|---|---|---|
Django web project | ✔ | ✔ | ✔ | ✗ | ✔ | ✔ | ✔ | ✔ |
Bottle web project | ✔ | ✔ | ✔ | ✗ | ✔ | ✔ | ✔ | ✔ |
Flask web project | ✔ | ✔ | ✔ | ✗ | ✔ | ✔ | ✔ | ✔ |
Generic web project | ✔ | ✔ | ✔ | ✗ | ✔ | ✔ | ✔ | ✔ |
Azure | 2017+ | 2015 | 2013 Comm | 2013 Desktop | 2013 Web | 2013 Pro+ | 2012 Pro+ | 2010 SP1 Pro+ |
---|---|---|---|---|---|---|---|---|
Deploy to web site | ✔ | ✔ | ✔ | ✗ | ✔ | ✔ | ✔ | ✔2 |
Deploy to web role | ✔ | ✔ | ✔ | ✗ | ✔4 | ✔4 | ✔3 | ✗ |
Deploy to worker role | ? | ? | ? | ✗ | ✔4 | ✔4 | ✔3 | ✗ |
Run in Azure emulator | ? | ? | ? | ✗ | ✔4 | ✔4 | ✔3 | ✗ |
Remote debugging | ✔ | ✔ | ✔ | ✗ | ✔6 | ✔8 | ✔8 | ✗ |
Attach Server Explorer | ✔ | ✔ | ✔ | ✗ | ✔7 | ✔7 | ✗ | ✗ |
Django templates | 2017+ | 2015 | 2013 Comm | 2013 Desktop | 2013 Web | 2013 Pro+ | 2012 Pro+ | 2010 SP1 Pro+ |
---|---|---|---|---|---|---|---|---|
Debugging | ✔ | ✔ | ✔ | ✗ | ✔ | ✔ | ✔ | ✔ |
Auto-complete | ✔ | ✔ | ✔ | ✗ | ✔5 | ✔5 | ✔ | ✔ |
Auto-complete for CSS and JavaScript | ✔ | ✔ | ✔ | ✗ | ✔5 | ✔5 | ✗ | ✗ |
Debugging | 2017+ | 2015 | 2013 Comm | 2013 Desktop | 2013 Web | 2013 Pro+ | 2012 Pro+ | 2010 SP1 Pro+ |
---|---|---|---|---|---|---|---|---|
Debugging | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
Debugging without a project | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
Debugging - attach to editing | ✔ | ✔ | ✔ | ✔ | ✗ | ✔ | ✔ | ✔ |
Mixed-mode debugging | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✗ |
Remote debugging (Windows, Mac OS X, Linux) | ✔ | ✔ | ✔ | ✔ | ✗ | ✔ | ✔ | ✔ |
Debug Interactive window | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
Profiling | 2017+ | 2015 | 2013 Comm | 2013 Desktop | 2013 Web | 2013 Pro+ | 2012 Pro+ | 2010 SP1 Pro+ |
---|---|---|---|---|---|---|---|---|
Profiling | ✔ | ✔ | ✔ | ✗ | ✗ | ✔ | ✔ | ✔ |
Test | 2017+ | 2015 | 2013 Comm | 2013 Desktop | 2013 Web | 2013 Pro+ | 2012 Pro+ | 2010 SP1 Pro+ |
---|---|---|---|---|---|---|---|---|
Test explorer | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✗ |
Run test | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✗ |
Debug test | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✗ |
Django Projects In Visual Studio Code
Git support for Visual Studio 2012 is available in the Visual Studio Tools for Git extension, available on the Visual Studio Marketplace.
Deployment to Azure Web Site requires Azure SDK for .NET 2.1 - Visual Studio 2010 SP1. Later versions don't support Visual Studio 2010.
Support for Azure Web Role and Worker Role requires Azure SDK for .NET 2.3 - VS 2012 or later.
Support for Azure Web Role and Worker Role requires Azure SDK for .NET 2.3 - VS 2013 or later.
Django template editor in Visual Studio 2013 has some known issues that are resolved by installing Update 2.
Requires Windows 8 or later. Visual Studio 2013 Express for Web doesn't have the Attach to Process dialog, but Azure Web Site remote debugging is still possible using the Attach Debugger (Python) command in Server Explorer. Remote debugging requires Azure SDK for .NET 2.3 - Visual Studio 2013 or later.
Requires Windows 8 or later. Attach Debugger (Python) command in Server Explorer requires Azure SDK for .NET 2.3 - Visual Studio 2013 or later.
Requires Windows 8 or later.