When comparing PyCharm vs Visual Studio Code, the Slant community recommends PyCharm for most people. In the question“What are the best Python IDEs or editors?” PyCharm is ranked 1st while Visual Studio Code is ranked 5th. The most important reason people chose PyCharm is:
PyCharm has CVS, Git, Subversion and Mercurial integration.
Ranked in these QuestionsQuestion Ranking
Pro Version control integration
PyCharm has CVS, Git, Subversion and Mercurial integration.
Pro Catches run-time information when running the code
PyCharm can leverage run-time information when running your application with the built-in debugger to figure out what types can possibly be passed to which functions, etc.
Pro One of the best autocompletion engines around
PyCharm has two types of autocompletion: structural completion and word expansion.
Both types of autocompletion work extremely well, have little to no problems and are quite fast even when loading suggestions on the go.
Pro Free version available
There's a community edition (with limited features) that's free to use. You can also get a 30-day trial of the Professional edition.
Pro Great pip support
PyCharm offers great pip integration. When opening a project it automatically checks for a
requirements.txt file in the root of the project. If it's found, it checks if all the libraries are available in the interpreter. If one or more libraries are missing, it issues a warning and asks whether you want to install any missing libraries.
Pro Excellent refactoring support
There are many refactoring options including renaming and changing signature across entire projects. It also includes the an ability to preview changes before committing and exclude anything unwanted.
Pro Automatically figures out what test to run based on the method the cursor rests at a given time
PyCharm, based on what method or class the cursor rests, can figure out what tests to run and perform them with a keyboard shortcut or two, without breaking up the flow and need to switch to a command line interface.
Pro Excellent integration with debugging tools
All the debugging can be done inside the IDE. Breakpoints in the code can be added using keyboard shortcuts or the mouse. When the code is executed through the debugger a toolbar pops up with all the relevant context needed for the debugging process.
The whole process is smooth and painless and you don't even have to switch windows to do the debugging.
Pro Great for navigating large codebases
PyCharm has amazing code navigation implementations. It supports both goto symbol and goto declaration. The former finds classes, variables, functions, etc by name. While the latter is used by moving the cursor on top of a symbol and by using the mouse or a keyboard combination it finds the declaration of that symbol and takes you there.
Both of these features are extremely helpful when consulting large code-bases and when trying to understand an API written by someone else.
Pro Supports installing third party libraries
No need to go to the command line to download a new package, PyCharm has an easy system to browse, download, and update third party packages.
Pro Sophisticated static analysis tools
Pro Remote debugging over ssh coupled with automatic deployment creates a streamlined workflow
The professional version allows remote debugging over ssh, which together with automatic deployment creates a streamlined workflow.
Pro Built-in Django support
Pycharm has excellent django support, from templating to management commands, it has it all.
Pro Vim mode for people used to Vim commands
IdeaVim supports motion keys, insert mode commands, marks, registers, visual mode commands, vim regexps, key mapping, macros, digraphs, some ex and :set commands. You can find a full comparison in the IdeaVim reference manual.
Pro Free student access to Professional Edition
With a valid .edu address students can register to use the Professional edition and enjoy all the perks of the full paid version for free.
Though it should be mentioned that the with the free student acess you cannot use PyCharm for any commercial purposes, even accepting donations for an open source project.
Pro Easy to optimize code with built-in profiling tools
If you have a yappi profiler installed on your interpreter, PyCharm starts the profiling session with it by default, otherwise it uses the standard cProfile profiler.
Pro TypeScript integration
There is very solid TypeScript integration in Visual Studio Code. Both are developed by Microsoft and VSC itself is written in TypeScript.
Pro Extendable through plugins
Visual Studio Code comes fairly complete out of the box, but there are many plugins available to extend its functionality.
Pro Embedded Git control
Visual Studio Code has integrated Git control, guaranteeing speed, data integrity, and support for distributed, non-linear workflows.
Pro Integrated debugging
Pro Ready to use out of the box
You don't need to configure and add plugins before being productive. However, you can add plugins if needed but for the basics you're well covered.
Pro Integrated terminal
There's no need to press alt+tab to go to a terminal: it is directly integrated into the editor.
Shift+~ is a handy hotkey to toggle the integrated terminal.
Pro Great performance
For a 'wrapped' web-based application, Visual Studio Code performs very well.
Pro Integrated task runners
Task runners display lists of available tasks and performing these tasks is as simple as a click of the mouse.
Pro Updated frequently
There's a new release of Visual Studio Code every month. If you are one of the insiders then releases are daily.
Pro ESLint integration
ESLint integrates great. You can define your rules trough .eslintrc.* as usual and vs code will autofix your code on save. So your code is always in style.
Pro Custom snippets support
Snippets are templates that will insert text for you and adapt it to their context, and in VSC they are highly customizable.
Pro Active development
It's really nice to see how the code editor evolves. Every month there is a new version with great communication of new features and changes.
Pro Libre/open source
Released under the MIT License.
Pro Huge community behind it
The ease of getting assistance and finding tutorials is increasing as the community grows.
Pro Fast and powerful
VS-Code has the speed of Sublime and the power of WebStorm. Perhaps this is the best software that Microsoft has ever created.
Pro High fidelity C# plugin
The Omnisharp plugin is very powerful providing full sln, csproj, and project.json support.
Pro Support RTL languages
It supports pretty web rtl languages like arabic languages when most of other editors don't support it.
Pro It has gotten really good
All it takes is one stop for all the features many people need.
Pro Inline definition picking and usages finding
These features allow you to have a glance at code without opening it as a whole in a separate tab. Moreover, editing is allowed.
Pro JS typechecking
It leverages TypeScript compiler functionality to statically type check JS (type inference, JSDoc types) with
Pro Python support
Excellent Python plugin, originally created by Don Jayamanne, now hired by Microsoft to extend and maintain the extension.
Pro Good support for new Emmet syntax
Con Very high memory usage
Con Does not support inline plots
Spyder supports the inline plot function of matplotlib, not the case for PyCharm.
Con Rendering is awful
Con Vim mode is limited
Con Not suitable to edit project's files written in other languages
Con Some relatively basic functionality requires paid license
Con Odd Autosave "feature", can't be disabled fully
PyCharm automatically saves your files for you, always, without telling you. You can't disable this. There's a way to indicate if a file has been modified via an indicator in the tab (not enabled by default - why?).
If you exit it won't ask you if you want to save the modified file. Totally unintuitive and contrary to all other established workflows. It's ok to try something new, but give users the option to have the "normal" behaviour of any other IDE/editor out there. Can be a deal breaker for those that need to know/have control over when they save their files. (PyCharm offers a history to undo the automatic save, but why force a user to undo something with extra steps that shouldn't have happened in the first place?)
Con Can not be integrated with external linters, like Pylint, Flake8, etc.
Sublime Text has SublimeLinter, Vim has Syntastic, PyCharm has nothing.
Con Not possible to run scripts in a single console
Con The autocomplete and code check is not as powerful as the one on WebStorm
Sometimes it doesn't tell you if you made a typo in a method name or if a method is not used and several other important features.
Con Embedded Git isn't powerful enough
You can do nothing but to track changes, stage them and commit. No history, visualization, rebasing or cherry-picking – these things are left to git console or external git client.
Con Project search limits results
Because file search is so slow your results are limited in order to simulate a faster search.
Con No support for tiled/grid editor layouts
It can be configured for rows of editors, or columns of editors, but not both simultaneously. The development team has explicitly said this is not a priority.
Con Is not an IDE, is a text editor
VS Code is a general code/scripting IDE built to be lightweight and for people familiar with their language of choice, not directly comparable to Visual Studio in power or scope.
Con Memory hog
Allegedly, VS Code is "lightweight". Yet, running multiple instances of it at once, you may get many "out of memory" messages from Windows despite 16 GB RAM. (While of course also running other things. The point is the comparison with some other IDEs/editors where running them alongside the same number of other applications doesn't cause Windows to run out of memory)
Con Very bad auto import
Con A "me too" offering from MS, far behind other well established editors that it attempts to clone
Other IDEs specific to a language often offer better tools for deep programming.
Con Slow launch time
Than it's competitors, e.g. Sublime Text.
Con Emmet plugin often fails on even simple p tags
Con Have no good default js style analyzer
In WebStorm there is analyzer that checks for warnings and highlight this in yellow, here I cannot find or add it even with plugins. It is possible to have it as errors with linter but while you are actively changing file that's not very nice.
Con File search is extremely slow
It's absolutely not possible to use this tool with big projects given how long it takes to search for files.