Similar to IntelliSense, interactive debugging in Python is a fairly recent development. Make a subclass and start typing some method overrides.Add a value to a list that’s been passed into a function.Call a function with different arguments and look at the return values.Put different types into a tuple and then unpack them later.We’ve spent a lot of time optimizing our analysis for common Python patterns. You can mouse-over any variable to see what types it could be at that point, or “dot-through” to see its members.

Using full-program analysis, we track variables from the first time they are initialized to every place they are used. In Visual Studio, we provide this deep understanding for you. Most editors do not provide helpful tips and force you to keep your entire program’s operation in your own head. This saves a lot of time while coding, but it requires a deep understanding of your program and every bit of help from your editor is important. Unlike many other languages, Python code does not need you to specify types everywhere. Python developers have not been so lucky, having to be content with only minimal code suggestions and basic syntax highlighting. Visual Studio has always had great IntelliSense for all of its languages, so if you’ve been coding in C# or VB for the last fifteen years you aren’t even impressed anymore. I know, we talk about IntelliSense all the time. In this post I want to talk about some of the reasons to consider using Visual Studio next time you are working in Python. You can find all the details and some video walkthroughs, documentation, and other resources on, and the post announcing Python Tools 2.1 and Python Tools 2.2 beta. Python Tools for Visual Studio (PTVS) are available to help throughout Visual Studio in all the places you’d expect, from editing and IntelliSense, to debugging, profiling, and publishing to Azure. Recently, Visual Studio 2015 was released with support for Python.

How to use python in visual studio 2010