Live data from Hacker News

Why Write Python in Visual Studio?

blogs.msdn.com

41–50 of 115 posts

Re: Why Write Python in Visual Studio?

#41
post #36

Earlier quoted context omitted.

Microsoft + Python = Ironpython. !Cred.

I am giving Microsoft some room for redemption for many mistakes made in the Ballmer era. This support for Python in VS may be a step in that direction.

Agreed. Clearly I'm being unfair, but I think I may not be alone in my aversion to the old Ballmer brands. Perhaps SN should "do an Edge" on the VS moniker.

Re: Why Write Python in Visual Studio?

#42
post #3

I'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.

I wouldn't be surprised if they added this to VS Code, which is available for mac. That would be nice.

Re: Why Write Python in Visual Studio?

#43
post #5

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.

I remember seeing that you can simultaneously debug python and c extensions in visual studio. That's pretty impressive. If PyCharm has a similar feature, I'm not aware of it.

http://www.hanselman.com/blog/OneOfMicrosoftsBestKeptSecrets...

Re: Why Write Python in Visual Studio?

#44
post #5

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.

I'm curious how smart auto-complete in PyCharm compares to IntelliSense here. The claim that a variable's lifecycle is followed from beginning to end is interesting. I'm finding that the JetBrains autocomplete knows what a variable's type is maybe the first or second time it's mutated, but often loses track. It's had the positive effect of lessening the amount I rely on re-assigning values to the same variable, but I wonder if IntelliSense can actually deliver here.

Re: Why Write Python in Visual Studio?

#45
post #5

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.

Me too. The only concern I have was that PyCharm somehow still depends on Java 1.6 rather than Java8 :(

Re: Why Write Python in Visual Studio?

#46
post #3

I'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?

Certainly a no go for developers who work on Macs - as VisualStudio is strictly Windows only still :(

Re: Why Write Python in Visual Studio?

#47

I don't want to be forced to login to software before I use it. Also, Microsoft can't be trusted. Look at the keylogger in Windows 10, for example. PyCharm is a good Python IDE. You can get a lot of these features in Emacs (or try Spacemacs), or Vim, or Sublime (with plugins).

>I don't want to be forced to login to software before I use it.

Then don't, you don't have to log in. That's just to help roam your settings and hook up to Azure if you've got an account.

If you don't want these features, just click "Don't Sign In".

Re: Why Write Python in Visual Studio?

#48

I don't want to be forced to login to software before I use it. Also, Microsoft can't be trusted. Look at the keylogger in Windows 10, for example. PyCharm is a good Python IDE. You can get a lot of these features in Emacs (or try Spacemacs), or Vim, or Sublime (with plugins).

You mean the "keylogger" than only tracks search queries & auto-correct to better optimize algorithms, which Google and Apple both do. Sure.

You also don't -have- to sign in. So your post is just nonsense.

Re: Why Write Python in Visual Studio?

#50

Earlier quoted context omitted.

Works fine in a Windows VM.

There really is no point in using OSX if you need to keep some tools in Windows and some others in Mac.

That's not true at all. I'd much, much rather have OS X's build of Photoshop even when using it with a game I'm writing in C# and it's much easier to quickly munge things using rbenv-managed Ruby than to fight with cygwin or RubyInstaller.
Post reply on HN