So let’s review a few other popular alternatives and how they compare to Visual Studio Code. It’s hard to judge a code editor without context. While this is nice, how does it stack up against the other players in the code editor game? Pros, Cons, and Alternatives With the right settings, extensions, and configured shortcut keys, it can easily become a full-stack workstation. There are productivity, custom debuggers, code linters, ssh-terminals, prettifies, and DevOps pipeline connections.Īlthough the major feature of Visual Studio Code is being a code editor, with the addition of extensions, it becomes more than just a code editor. With the addition of framework, library, and/or language plugin extensions, you can leverage this even further with ready-made boiler-plates.Īnother major thing about the extension marketplace for Visual Studio Code is that it’s not limited to just code. intelliSense is a form of predictive coding. In addition to this, there is intelliSense but built into the code editor. It’s built into the design and your desired workspace set up. You don’t need to have multiple screens to run the different consoles and rearrange them each time you need to minimize something. This makes the process of bug tracking, and code run-throughs a lot easier and faster. Unlike many other code editors, Visual Studio Code has an in-built debugger, making the development flow less ‘clicky’ and maintains a single view with code and debugger. This means that it works on Windows, Linux, and macOS. Visual Studio Code is free, open-source, and cross-platform. However, there are few distinct features that tip a developer’s preference over towards Visual Studio Code. This simple trick should solve the problem.But why is it so popular? On the surface, it looks just like a typical code editor. Pressing F5 you can now debug your code without problem.įigure 4: Debugging in VSCode after installing required modules Once you installed modules using the very same version chosen as interpreter in VSCode, you are ready to go.
#Python visual studio code debugger doesnt work install#
Once you realize this, solution is straightforward, just install module with pip using the same version of Python chosen as interpreter (Figure 2) using directly python.exe correct version as shown in Figure 3.įigure 3: Install modules with right version of pip Since Visual Studio Code can use whichever version of Python in your system, you need to install modules for that specific version used. This allows you to choose which Python version you want to use, but clearly, when you press F5 that specific version is used and probably you did not install required module in that specific version.
When you edit Python files in Visual Studio Code you should select interpreter path command to specify which version of Python you want to use, as showed in Figure 2: The problem arise because Visual Studio Code is not using the very same installation of python you are using from your command line / terminal. One of the most annoying problem is receiving a no module named xxx error when you already installed that module with pip.įigure 1: No module error when running Python code in Visual Studio Code
I’m not a Python expert, but I used it more often these days and I use Visual Studio Code with Python extension to author my scripts.
0 kommentar(er)
