I write Python professionally, and it will be pretty hard to get me away from PyCharm. I don't see anything in the blog post that indicates a feature PyCharm doesn't already have.
> a feature PyCharm doesn't already have It's free. I'm sure there are a lot of Python developers who already have a full-featured IDE they love, but then there are also people (like me) who sometimes write Python and just use Sublime Text or Vim. Or even Eclipse.
Why Write Python in Visual Studio?
21–30 of 115 posts
Re: Why Write Python in Visual Studio?
#22I'm a .NET developer so to me this is a slam dunk. How does the Python crowd feel though? I'd guess the majority tend to be Microsoft-adverse. Why wouldn't you use VS when it seems to be so ahead of the competition?
IntelliSense is pretty good, sure, but emacs is a superior development environment in nearly every other aspect.
Re: Why Write Python in Visual Studio?
#23I'm a .NET developer so to me this is a slam dunk. How does the Python crowd feel though? I'd guess the majority tend to be Microsoft-adverse. Why wouldn't you use VS when it seems to be so ahead of the competition?
If they had VS on OSX I'd definitely give it a shot. Unfortunately, they don't, yet.
Re: Why Write Python in Visual Studio?
#24For those who have used this: - Does it perform better than PyCharm? - How is Windows working for you as an OS (to develop Python on)?
I've developed a few pieces of software on Windows and by far, the most painful thing I had to do install Visual Studio Express to compile some of the C extensions. I used Pycharm on Windows, so it pretty much abstracted away tasks like making virtualenvs, setting up environment variables, etc.
Re: Why Write Python in Visual Studio?
#25Some things that annoy me:
- Reading intellisense python documentation in the mouse over window is really tedious. There is an object window that can display documentation for your classes, but not from libraries.
- Rendered docs are much easier to read. Spyder did this very well. With PTVS I'm looking at the docs online for numpy and matplotlib. With spyder I just ctrl+I and it displays using sphinx very nicely.
- I was not able to get IPython to cooperate with displaying plots in separate windows in executing scripts as easy in PTVS compared to Spyder.
- Being able to commit and push to github is a great feature.
- Spyder had superior debugging features in terms of examining array data throughout the debug process. Make plots just by right clicking the object in the variables window. Very useful for making sure a step for a scientific algorithm is doing what I intended.
I'm hoping more features like the above will be added over time. However I'm looking at going back to Spyder + some git plugin or tool, or switching to PyCharm.
Re: Why Write Python in Visual Studio?
#26Re: Why Write Python in Visual Studio?
#27I'm a .NET developer so to me this is a slam dunk. How does the Python crowd feel though? I'd guess the majority tend to be Microsoft-adverse. Why wouldn't you use VS when it seems to be so ahead of the competition?
Re: Why Write Python in Visual Studio?
#28Earlier quoted context omitted.
When you say ahead of the competition, what do you mean? Ive used it before (2005, 2008, 2010), but it was just another IDE. How have things improved?
I work in Visual Studio exclusively for my day job the last 8 years so my experience is pretty limited. But every time I try out other languages and IDEs on my own time, I'm almost shocked at how hard the tools are to work with compared with Visual Studio. VS has excellent intellisense. Compile and runtime errors are clearly pointed out, usually with helpful error messages. And real-time debugging and being able to s…
Re: Why Write Python in Visual Studio?
#29I'm a .NET developer so to me this is a slam dunk. How does the Python crowd feel though? I'd guess the majority tend to be Microsoft-adverse. Why wouldn't you use VS when it seems to be so ahead of the competition?
IntelliSense is pretty good, sure, but emacs is a superior development environment in nearly every other aspect.
Re: Why Write Python in Visual Studio?
#30Having been using Python professionally for about 8 years now, i've been playing with PTVS and finally think its ready for public consumption - if you've tried it more than 9 months ago, be sure to try again - it is lightyears better, especially when it comes to things like remote debugging and managing venvs.
Documentation is still a bit lacking here and there when it comes to getting PTVS to play nicely with other debuggers like pdb and werzkeug, but overall, i cant wait to see the project and the team continue on this effort.