Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Why Write Python in Visual Studio?

blogs.msdn.com

Post reply on HN
Print view View original

51–60 of 115 posts

Re: Why Write Python in Visual Studio?

#51

Post by blackbeard »

RA_Fisher wrote: post #49

And one really great reason not to use it, the license. At any point they can yank it away from you, why invest time into learning something like that?

They have made at least two attempts to do that in the past as well with dropping the cheap versions of visual c# 2003 and then trying to yank the desktop version of visual studio 2013 express so a fair observation.

Plus I think you have to sign in now to maintain your license in community edition and the SDK is no longer standalone.

Re: Why Write Python in Visual Studio?

#52

Post by josephcooney »

sswaner wrote: post #36
vegabook wrote: post #31

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.

I don't think this has much to do with the change of the guard at the top. Iron Python was started in 2008, and Python tools for VS was first released in 2011.

Re: Why Write Python in Visual Studio?

#53

Post by Cyph0n »

compostor42 wrote: post #21
TillE wrote: post #17

Earlier quoted context omitted.

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

JetBrains released a free community version: https://www.jetbrains.com/pycharm/download/

They also provide a free 1 year educational license for all of their products to students.

Re: Why Write Python in Visual Studio?

#54

Post by kelvin0 »

Last time I tested PTVS, running any simple script was 100x slower than running it within Wing IDE (professional) which I was I used 99% of the time. This pretty much killed the idea of using Python in VS, unfortunately (for me anyways).

Re: Why Write Python in Visual Studio?

#55

Post by stillsut »

numo16 wrote: post #34
stillsut wrote: post #33

I work at a .Net shop and wanted to build a developer tool with python for my colleagues. None of them have a python interpreter so it needs to compile to an .exe I've googled for hours on how to do this with IronPython but the information is incredibly sparse and outdated. Is there any way to do this currently?

Perhaps this will point you in the right direction: http://www.decalage.info/en/python/py2exe

Thanks, I'd like to integrate with .net though, maybe with WPF. That's why I'd like to use IronPython.

Any MS / Python people?

Re: Why Write Python in Visual Studio?

#56

Post by FilterSweep »

partiallypro wrote: post #48
JoshMnem wrote: post #37

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.

Bits and pieces of both your comments are correct..... Apple and Google are both complicit in it as well. the issue with your comment is "only" - sure, they're optimizing algorithms, but its a symptom of not reading Terms & Conditions to believe they aren't also associating your search query with some sort of identifier. It's too easy not to implement this.

Re: Why Write Python in Visual Studio?

#57

Post by farresito »

eropple wrote: post #50
farresito wrote: post #39

Earlier quoted context omitted.

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.

That comes as a surprise. I expected Photoshop to be very similar between Mac and Windows. What's the biggest difference?

Re: Why Write Python in Visual Studio?

#58

Post by S4M »

atilaneves wrote: post #10
na85 wrote: post #8

Earlier quoted context omitted.

IntelliSense is pretty good, sure, but emacs is a superior development environment in nearly every other aspect.

...And you get can get autocompletion in Emacs as well, so there's that. Before you ask, I use jedi.

I use emacs with jedi too, but the auto-completion is not so good. For example, if my code is:

   def function1(x):
      variable1 = x+1
      return variable1**2

   def function2(x):
      variable2 = 2*x
      return 5+v...
And I get two auto-completion choices: variable1 and variable2, while only variable2 is logical.

Re: Why Write Python in Visual Studio?

#59

Post by S4M »

ohitsdom wrote: post #14
na85 wrote: post #8

Earlier quoted context omitted.

IntelliSense is pretty good, sure, but emacs is a superior development environment in nearly every other aspect.

I've never used emacs so am completely ignorant. What makes emacs superior? All I know is the speed that can come with keyboard shortcuts.

That, and the fact that it's very easy to extend it with Emacs Lisp. I know that it's possible to write extensions for most of the IDEs or text editors out there, but the degree of customization is higher with emacs, mainly because emacs is basically couple of primitive functions written in C + a lisp interpreter (also written in C) and the rest is written in lisp, so you have access to everything emacs has to offer if you want to customize it.

Re: Why Write Python in Visual Studio?

#60

Post by eropple »

farresito wrote: post #57
eropple wrote: post #50

Earlier quoted context omitted.

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.

That comes as a surprise. I expected Photoshop to be very similar between Mac and Windows. What's the biggest difference?

The application's similar, but the drivers aren't. Wacom's drivers and configuration management are a lot more finicky under Windows. Another helpful thing: Core Audio is about as fast as ASIO is under Windows, making music and SFX more pleasant to work on here--even, again, when writing a game in C#. (Even discounting that Logic doesn't run at all under Windows.)

It also has the nice side effect of not making me hate the computer I'm using and the project I am working on. The more things I have to touch on Windows, the more unhappy I am; I find it to be unpleasant and death-by-a-thousand-cuts draining to use for more than casual use (I own a Surface Pro 3, but only because I got it very cheap). There are two applications open in my Parallels virtual machine: Sublime Text (for editing YAML files) and Visual Studio for working on code--it's the minimal set of things I have to touch to use C# for development.

Post reply on HN