Debugging with custom environment variables.Debugging with support for shebang (windows).Debugging remote processes (attaching to local and remote process).Debugging Multiple threads (Web Applications - Flask, etc) and expanding values (on Windows and Mac).Debugging with support for local variables, arguments, expressions, watch window, stack information, break points.View signature and similar by hovering over a function or method.Renaming, Viewing references, Going to definitions, Go to Symbols.Code formatting (autopep8, yapf, with config files).Linting (PyLint, Pep8, Flake8 with config files and plugins).This is the go to extension for all things Python related. Extensions are all installed simply by bringing up the command palette ( cmd + shift + p) and typing ext install.
Today we'll be looking at how we can optimise the editor with a number of different extensions (or plugins if you're coming from Sublime) that will make writing Python a more enjoyable experience. Visual Studio Code reached it's version 1.0 milestone not long ago, and is starting to prove itself to be quite a powerful replacement for either Sublime Text or Atom, particularly for Python development. That was until a new challenger appeared. Still, the interface was extremely slick, and the theme support was great, so I persevered with it. Responsiveness became an issue the larger the project became (particularly from an autocomplete standpoint), and numerous other niggles. The debugging package that was suggested stopped working randomly. I've been a massive fan of Sublime Text for years now, and although I switched across to Atom earlier this year for a bit of a trial, there were a lot of things I just missed from my setup in Sublime. When writing code, everyone has a preference for their favourite editor of choice.
0 kommentar(er)
