1

I used PyCharm for quite a while until someone suggested VSC. I've been using VSC ever since. I'm not sure which one to use for Python development. Here are some pros and cons I've found.

VSC

Pros

  • Has plugins, allowing for enhanced development.
  • Supports seemingly infinite languages.

Cons

  • PyLint can get annoying at times, and you can't turn it off without bad issues¹.
  • It's hard to run.

PyCharm

Pros

  • It's designed mainly for python.
  • You can easily run python files

Cons

  • It's designed mainly for python. There isn't too much support for other languages.
  • It's buggy with changing the interpreter. It doesn't save properly, meaning that the interpreter you choose when you make a project is usually the interpreter you

¹You can't run it without spending 2 minutes setting up the shell at the bottom.

  • 2
    What OS? Honestly, Notepad++ (or some comparable Linux editor) along with the standard interactive interpreter have been fine enough for me for vast majority of the Python code I've written/worked with. Few times I've used Visual Studio (the big one -- being primarily a C++ dev, i've got a few versions around) with Python tools installed... I guess it worked alright, but since I mostly use Python for quick prototyping or answering SO questions, it was usually too much (compared to adding a tab to already open text editor, and popping up a new console if at all needed). – Dan Mašek Nov 10 '18 at 23:51
  • As a side note: Get familiar with the documentation of whatever language/library you use, learn to understand what the code you write does. Then all you really need is a piece of paper and something to write with (when I was a kid, that was what I did most of the time, since for many years, getting a machine it was meant for was out of question -- I could use it once in a long while). | "spending 2 minutes setting up the shell" -- write a script. And 2 minutes -- IMHO inconsequential, considering how much time you'll spend working on the code. – Dan Mašek Nov 10 '18 at 23:57
  • And finally, I'd say try all the possibilities and find out what suits you the best. I've worked at Skype in the C++ backend team, writing server code running on Debian in production. We had people using Vi, people using Emacs, people developing exclusively on remote machine as well as people developing on their own machines, people using Eclipse, people using KDevelop, people working on Macs, and who knows what else. That was a team of around 15 devs and it worked without issues -- we had a standardized build system, but what you used for editing was basically irrelevant. – Dan Mašek Nov 11 '18 at 0:11
  • @DanMašek Windows 7 – Person Nov 11 '18 at 2:23
  • 1
    ... That being said, go with whichever you are familiar with. There _may_ be some obscure feature which one offers, but the other not, but that's unlikely to outweigh the advantages of familiarity. Btw, since you are new, I will tell you that your (great) question, is off topic as it stands, please read How to Ask. We expect you to give us a list of requirements, from which we can recommend some software, not to help you choose. Such questions are always closed. I would advise you to reword this one. Welcome aboard, though; we need more Python help around her :-) – Mawg Nov 29 '18 at 8:01
1

The biggest difference between PyCharm and Visual Studio code is that PyCharm is an IDE and VS code is a text editor. That doesn't mean that one is better than the other, but PyCharm is geared more toward large projects, while VS code is geared more towards smaller projects. As with all code editor choices, it's largely based on personal preference which one you use, so pick the one you're more comfortable with (or use both).

  • VS Code is an IDE – Mawg Nov 29 '18 at 8:02
  • The boundary between IDE and editor is very, very fuzzy. VS Code is definitely closer to IDE than Notepad++. Sometimes you can find a feature in VS Code (especially with extensions) that some bigger IDE doesn't have. Regardless of what you think of as the boundary (if any), it's just not very useful to say "this one's an IDE and that one's an editor" when OP has obviously used both and to them both are under consideration. – John Y Nov 29 '18 at 23:31

Your Answer

By clicking "Post Your Answer", you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.