best kept secret? How did it end up in an article here then?
NSA whistleblower...
:)
Python Tools for Visual Studio
61–70 of 134 posts
Re: Python Tools for Visual Studio
#62I love Visual Studio but after having worked with python quite a lot and being involved in the local developer community (IN NEOhio, NYC, and starting into Southern Maine) I think I've only ever meet two python developers who used windows as there development Os. I'm not holding my breath but if MS would port VS to OS X/Linux it would be really cool. I don't know that a good business case could be made for it though.
I agree and am in the same boat. I don't mind windows, but for dev, linux is much more convenient. Also wanted to say hello from NEO.
Re: Python Tools for Visual Studio
#63best kept secret? How did it end up in an article here then?
Insert "LOL @ MICRO$LOTH CAN'T EVEN KEEP THEIR OWN SECRETS"-type comment here?
Re: Python Tools for Visual Studio
#64This doesn't even mention the most awesome feature of PTVS 2.0: mixed-mode debugging, which provides an integrated experience for debugging mixed Python/C processes. See https://pytools.codeplex.com/wikipage?title=Mixed-mode%20deb... for details. Disclaimer: I used to work on IronPython.
Can you expand a bit on how that works in principle ? Can you make it work with a standard python or did you need to insert probes' into the python interpreter to catch when it goes form C to Python and vice et versa
Re: Python Tools for Visual Studio
#65This doesn't even mention the most awesome feature of PTVS 2.0: mixed-mode debugging, which provides an integrated experience for debugging mixed Python/C processes. See https://pytools.codeplex.com/wikipage?title=Mixed-mode%20deb... for details. Disclaimer: I used to work on IronPython.
Can you expand a bit on how that works in principle ? Can you make it work with a standard python or did you need to insert probes' into the python interpreter to catch when it goes form C to Python and vice et versa
VS 2012 added a new debugging framework for supporting debugging multiple code types at the same time. That model requires that the debugger work out of process - inspecting various data structures cross process and reporting them back to VS. That's different from how Python debuggers are usually built w/ sys.settrace and a debugger helper thread running in the process.
To accomplish that we require that we have symbols for the Python interpreter (which are typically available on python.org). The debug engine uses a combination of the native equivalent of sys.settrace, strategic breakpoints, and using the symbols to walk core Python data structures. There's a bunch of fun tricks for evaluating code when stopped at a Python frame and creating strings, ints, etc... when users type them into the watch window.
If you'd like to dig in more the source is at http://pytools.codeplex.com/SourceControl/latest under Python\Product\Debugger\DkmDebugger.
Re: Python Tools for Visual Studio
#66Earlier quoted context omitted.
On the other hand perhaps something could be done about Python so that we who are forced to develop Python on Windows stop being second-class citizens in the Python world? ButI agree. VS is an awesome IDE and the more operating systems it would be available on the better.
You are fighting various other teams in Redmond/power users that have issues with OSS and technology that's cross platform and not from the Mothership. Python/Iron Python would have been a great default language for administrative scripting , but nope, they had to reinvent the wheel with PowerShell. (I've had MVPs yell at me for discussing data analysis with Python, even on Windows.)
PowerShell is a very nice language in its own right, though.
Re: Python Tools for Visual Studio
#67Just Vi or Vim for me. Used VS, VB, Eclips years back, but now back to Vi/Vim for embedded and server environment. Have not missed any of IDE features at all.
Even better vi for vs http://visualstudiogallery.msdn.microsoft.com/59ca71b3-a4a3-...
Re: Python Tools for Visual Studio
#68Does anyone have experience with the free VS Shell mentioned in the article as the foundation for putting together a free of cost installation? How does it compare to VS Express? Why would there be two different free Visual Studio offerings...just to keep things locked down and rule out support for add-ins?
overgard is correct.
Our PTVS + integrated/isolated shell basically gives you a virtual "Python Express". However recently msft has moved away from the "Express" model to "Scenario" models. ie, VS for Phone, VS for Desktop, VS for Web, etc. and each includes all the tools and multiple languages you might need for that workload. We're hoping to include PTVS into the desktop & Web scenarios in the future.
[disclaimer: project lead]
Re: Python Tools for Visual Studio
#69Earlier quoted context omitted.
Is there any decent SSH daemon on Windows? And what shell does/would it run? cmd.exe?
Some people dislike it but I use Cygwin when I want access to the various unix standard tools on a Windows box (including the openssh daemon). http://www.cygwin.com/ The setup.exe is both the installer and the package manager.
I recommend trying out Mintty for Cygwin if you haven't already. I love it.
Re: Python Tools for Visual Studio
#70Earlier quoted context omitted.
...which would be detrimental to Microsoft. Limiting our options to theirs is precisely their goal by giving us a great IDE that only works on Windows. They're never gonna go it. They stand to win nothing from that.
I dunno, I might just be cost prohibitive to port, and likely wouldn't run as well.
Even on a modern, high-powered laptop, Visual Studio still runs slowly for me. Some actions inexplicably cause the UI to hang for a few seconds. I really appreciate how OSX seems to prioritize UI responsiveness, which doesn't seem to be the case in Windows.